Do you mean this one? > Is the memBytes counter under tsm1_cache used to determine the compaction and rejection events?
On Mon, Oct 3, 2016 at 11:31 AM, <[email protected]> wrote: > Hi Sean, > Thanks. Can you please look at my other query? > > > On Thursday, September 29, 2016 at 3:48:24 PM UTC-7, Sean Beckett wrote: > > If you don't have any subscriptions, you can ignore those stats for now. > > > > > > > subWriteDrop is supposed to be incremented only when the system could > not pass the write to the subscription channel used by Kapacitor. The code > currently increments subWriteOk or subWriteDrop on every write regardless > of whether there are any subscriptions setup. There's an open issue to fix > it. https://github.com/influxdata/influxdb/issues/7330 > > > > > > > > > > On Thu, Sep 29, 2016 at 3:00 PM, <[email protected]> wrote: > > Hi all, > > > > On my system, the subwriteDrop keeps increasing (as i keep ingesting > data). I do not have any subscriptions. Show subscriptions via the web > console shows nothing. Why does this value keep incrementing? > > > > > > > > As per the cache section of https://docs.influxdata.com/ > influxdb/v1.0/concepts/storage_engine/ , > > > > "The Cache exposes a few controls for snapshotting behavior. The two > most important controls are the memory limits. There is a lower bound, > cache-snapshot-memory-size, which when exceeded will trigger a snapshot to > TSM files and remove the corresponding WAL segments. There is also an upper > bound, cache-max-memory-size, which when exceeded will cause the Cache to > reject new writes. These configurations are useful to prevent out of memory > situations and to apply back pressure to clients writing data faster than > the instance can persist it." > > > > > > > > Does influxdb maintain a counter for these rejection events? Is the > memBytes counter under tsm1_cache used to determine the compaction and > rejection events? > > > > > > > > Thanks > > > > > > > > -- > > > > Remember to include the InfluxDB version number with all issue reports > > > > --- > > > > You received this message because you are subscribed to the Google > Groups "InfluxDB" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > > > To post to this group, send email to [email protected]. > > > > Visit this group at https://groups.google.com/group/influxdb. > > > > To view this discussion on the web visit https://groups.google.com/d/ > msgid/influxdb/45a7a7f0-d888-45dd-b11a-586dbde185ab%40googlegroups.com. > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > -- > > > > > > Sean Beckett > > Director of Support and Professional Services > > InfluxDB > > -- > Remember to include the InfluxDB version number with all issue reports > --- > You received this message because you are subscribed to the Google Groups > "InfluxDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/influxdb. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/influxdb/9300d9a9-1295-4f0b-848c-fa7f64fe3c17%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Sean Beckett Director of Support and Professional Services InfluxDB -- Remember to include the InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/CALGqCvOWyM8PMsL1zm-YXwJQonj%2Bb7aXtGZ%2BMSQrjE9yKKARcw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
