Changing influxdb configuration (max-values-per-tag = 100000) for influxdb set up as a GKE applicationKubernetes pod on Google Container Engine continually restarts, is never readyCan't shut down influxDB in KubernetesDisable WAL in influxdb v0.13 or force flushChange tag value in InfluxDBKubernetes pods failing all at onceMax values per tag limit exceeded InfluxDBInstalling InfluxDB on Kubernetes ClusterGetting Heapster and InfluxDB to communicatemax-values-per-tag limit exceeded Why getting error on TAG KEY ip_address only?Restore Influxdb backup inside docker compose container
What is the object moving across the ceiling in this stock footage?
How were these pictures of spacecraft wind tunnel testing taken?
Are there situations when self-assignment is useful?
Array Stutter Implementation
What are the benefits of cryosleep?
At what point in European history could a government build a printing press given a basic description?
Why colon to denote that a value belongs to a type?
If a person had control of every single cell of their body, would they be able to transform into another creature?
How do you say “buy” in the sense of “believe”?
Why is desire the root of suffering?
Tic-Tac-Toe for the terminal
I think I may have violated academic integrity last year - what should I do?
Rests in pickup measure (anacrusis)
Is there a down side to setting the sampling time of a SAR ADC as long as possible?
Which noble houses were destroyed during the Game of Thrones?
Is there any use case for the bottom type as a function parameter type?
I unknowingly submitted plagiarised work
Employer demanding to see degree after poor code review
Integrating an absolute function using Mathematica
How strong are Wi-Fi signals?
Do you play the upbeat when beginning to play a series of notes, and then after?
How bitcoin nodes update UTXO set when their latests blocks are replaced?
When do characters level up?
What is the 中 in ダウンロード中?
Changing influxdb configuration (max-values-per-tag = 100000) for influxdb set up as a GKE application
Kubernetes pod on Google Container Engine continually restarts, is never readyCan't shut down influxDB in KubernetesDisable WAL in influxdb v0.13 or force flushChange tag value in InfluxDBKubernetes pods failing all at onceMax values per tag limit exceeded InfluxDBInstalling InfluxDB on Kubernetes ClusterGetting Heapster and InfluxDB to communicatemax-values-per-tag limit exceeded Why getting error on TAG KEY ip_address only?Restore Influxdb backup inside docker compose container
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I took advantage of the GKE Application console to quickly spin up an instance of Influxdb in my existing GKE cluster. This allowed me to get started with influxdb with relative ease. However, after I started writing data to the cluster, I quickly ran into the 'Max values per tag exceeded limit'. Looking this up, I found articles that recommend setting of the 'max-values-per-tag' to 0 and restarting the influxdb. Problem is, given that I setup influxdb as a GKE application, I don't know if there is a way to change the configuration settings for influxdb via the GKE console or any other way. I did a kubexec to the influxdb pod but don't find this setting in the /etc/influxdb/influxdb.conf file. Even if I do change the file, I don't think the value will survive a restart of the pod since I don't believe this file is in a persistent volume.
Is there a way to change influxdb settings of my influxdb instance that I have spun using GKE application console.
This is the current contents of my /etc/influxdb/influxdb.conf file in the influxdb pod
[meta]
dir = "/var/lib/influxdb/meta"
[data]
dir = "/var/lib/influxdb/data"
engine = "tsm1"
wal-dir = "/var/lib/influxdb/wal"
influxdb google-kubernetes-engine
add a comment |
I took advantage of the GKE Application console to quickly spin up an instance of Influxdb in my existing GKE cluster. This allowed me to get started with influxdb with relative ease. However, after I started writing data to the cluster, I quickly ran into the 'Max values per tag exceeded limit'. Looking this up, I found articles that recommend setting of the 'max-values-per-tag' to 0 and restarting the influxdb. Problem is, given that I setup influxdb as a GKE application, I don't know if there is a way to change the configuration settings for influxdb via the GKE console or any other way. I did a kubexec to the influxdb pod but don't find this setting in the /etc/influxdb/influxdb.conf file. Even if I do change the file, I don't think the value will survive a restart of the pod since I don't believe this file is in a persistent volume.
Is there a way to change influxdb settings of my influxdb instance that I have spun using GKE application console.
This is the current contents of my /etc/influxdb/influxdb.conf file in the influxdb pod
[meta]
dir = "/var/lib/influxdb/meta"
[data]
dir = "/var/lib/influxdb/data"
engine = "tsm1"
wal-dir = "/var/lib/influxdb/wal"
influxdb google-kubernetes-engine
add a comment |
I took advantage of the GKE Application console to quickly spin up an instance of Influxdb in my existing GKE cluster. This allowed me to get started with influxdb with relative ease. However, after I started writing data to the cluster, I quickly ran into the 'Max values per tag exceeded limit'. Looking this up, I found articles that recommend setting of the 'max-values-per-tag' to 0 and restarting the influxdb. Problem is, given that I setup influxdb as a GKE application, I don't know if there is a way to change the configuration settings for influxdb via the GKE console or any other way. I did a kubexec to the influxdb pod but don't find this setting in the /etc/influxdb/influxdb.conf file. Even if I do change the file, I don't think the value will survive a restart of the pod since I don't believe this file is in a persistent volume.
Is there a way to change influxdb settings of my influxdb instance that I have spun using GKE application console.
This is the current contents of my /etc/influxdb/influxdb.conf file in the influxdb pod
[meta]
dir = "/var/lib/influxdb/meta"
[data]
dir = "/var/lib/influxdb/data"
engine = "tsm1"
wal-dir = "/var/lib/influxdb/wal"
influxdb google-kubernetes-engine
I took advantage of the GKE Application console to quickly spin up an instance of Influxdb in my existing GKE cluster. This allowed me to get started with influxdb with relative ease. However, after I started writing data to the cluster, I quickly ran into the 'Max values per tag exceeded limit'. Looking this up, I found articles that recommend setting of the 'max-values-per-tag' to 0 and restarting the influxdb. Problem is, given that I setup influxdb as a GKE application, I don't know if there is a way to change the configuration settings for influxdb via the GKE console or any other way. I did a kubexec to the influxdb pod but don't find this setting in the /etc/influxdb/influxdb.conf file. Even if I do change the file, I don't think the value will survive a restart of the pod since I don't believe this file is in a persistent volume.
Is there a way to change influxdb settings of my influxdb instance that I have spun using GKE application console.
This is the current contents of my /etc/influxdb/influxdb.conf file in the influxdb pod
[meta]
dir = "/var/lib/influxdb/meta"
[data]
dir = "/var/lib/influxdb/data"
engine = "tsm1"
wal-dir = "/var/lib/influxdb/wal"
influxdb google-kubernetes-engine
influxdb google-kubernetes-engine
asked Mar 24 at 7:41
boboverflowboboverflow
10916
10916
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I figured the answer myself. When creating the influxdb application from The GKE application console, GKE created a stateful set and a persistent volume for me.
The path /var/lib/influxdb is mounted on the persistent volume created for this influxdb instance which means that locating the influxdb.conf file in this location guarantees that it will survive pod restarts. So I copied the file originally located in /etc/influxdb/influxdb.conf into /var/lib/influxdb/influxdb.conf and edited it to add this line to the data section:
max-values-per-tag = 0
I then edited the stateful set via kubectl and set an additional environment variable INFLUXDB_CONFIG_PATH to /var/lib/influxdb/influxdb.conf
Editing the stateful set caused the influxdb pod to be recreated, and the new influxdb pod has the necessary configuration which now allows me to write an unlimited number of unique values per tag.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55321676%2fchanging-influxdb-configuration-max-values-per-tag-100000-for-influxdb-set-u%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I figured the answer myself. When creating the influxdb application from The GKE application console, GKE created a stateful set and a persistent volume for me.
The path /var/lib/influxdb is mounted on the persistent volume created for this influxdb instance which means that locating the influxdb.conf file in this location guarantees that it will survive pod restarts. So I copied the file originally located in /etc/influxdb/influxdb.conf into /var/lib/influxdb/influxdb.conf and edited it to add this line to the data section:
max-values-per-tag = 0
I then edited the stateful set via kubectl and set an additional environment variable INFLUXDB_CONFIG_PATH to /var/lib/influxdb/influxdb.conf
Editing the stateful set caused the influxdb pod to be recreated, and the new influxdb pod has the necessary configuration which now allows me to write an unlimited number of unique values per tag.
add a comment |
I figured the answer myself. When creating the influxdb application from The GKE application console, GKE created a stateful set and a persistent volume for me.
The path /var/lib/influxdb is mounted on the persistent volume created for this influxdb instance which means that locating the influxdb.conf file in this location guarantees that it will survive pod restarts. So I copied the file originally located in /etc/influxdb/influxdb.conf into /var/lib/influxdb/influxdb.conf and edited it to add this line to the data section:
max-values-per-tag = 0
I then edited the stateful set via kubectl and set an additional environment variable INFLUXDB_CONFIG_PATH to /var/lib/influxdb/influxdb.conf
Editing the stateful set caused the influxdb pod to be recreated, and the new influxdb pod has the necessary configuration which now allows me to write an unlimited number of unique values per tag.
add a comment |
I figured the answer myself. When creating the influxdb application from The GKE application console, GKE created a stateful set and a persistent volume for me.
The path /var/lib/influxdb is mounted on the persistent volume created for this influxdb instance which means that locating the influxdb.conf file in this location guarantees that it will survive pod restarts. So I copied the file originally located in /etc/influxdb/influxdb.conf into /var/lib/influxdb/influxdb.conf and edited it to add this line to the data section:
max-values-per-tag = 0
I then edited the stateful set via kubectl and set an additional environment variable INFLUXDB_CONFIG_PATH to /var/lib/influxdb/influxdb.conf
Editing the stateful set caused the influxdb pod to be recreated, and the new influxdb pod has the necessary configuration which now allows me to write an unlimited number of unique values per tag.
I figured the answer myself. When creating the influxdb application from The GKE application console, GKE created a stateful set and a persistent volume for me.
The path /var/lib/influxdb is mounted on the persistent volume created for this influxdb instance which means that locating the influxdb.conf file in this location guarantees that it will survive pod restarts. So I copied the file originally located in /etc/influxdb/influxdb.conf into /var/lib/influxdb/influxdb.conf and edited it to add this line to the data section:
max-values-per-tag = 0
I then edited the stateful set via kubectl and set an additional environment variable INFLUXDB_CONFIG_PATH to /var/lib/influxdb/influxdb.conf
Editing the stateful set caused the influxdb pod to be recreated, and the new influxdb pod has the necessary configuration which now allows me to write an unlimited number of unique values per tag.
answered Mar 25 at 5:41
boboverflowboboverflow
10916
10916
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55321676%2fchanging-influxdb-configuration-max-values-per-tag-100000-for-influxdb-set-u%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown