Discussion:
[influxdb] write failed for shard 143: engine: cache maximum memory size exceeded
Dmitriy Akulov
2016-10-05 21:11:46 UTC
Permalink
Hello, I dont completely understand what this error means. "write failed
for shard 143: engine: cache maximum memory size exceeded"
The server has 128GB of RAM and the config has default settings.
As far as I understand the "cache-max-memory-size" and
"cache-snapshot-memory-size" parameters are not related to RAM.
What exactly do they do? How they should be configured? Based on incoming
data? Based on RAM?

What should I do to fix this?

Also what exactly this message means "aborted level 1 group (0). compaction
in progress"?

Log that contains both errors
https://gist.githubusercontent.com/jimaek/5f7fe91cc5f689273bed64401e564db1/raw/5aea6861548a2f3d86940000f25576402bca29f5/gistfile1.txt

Thank you
--
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 influxdb+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
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/88679401-4e5b-4cee-9f20-80266333994f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Dmitriy Akulov
2016-10-07 10:26:51 UTC
Permalink
What are the downsides of increasing cache-max-memory-size. With 128GB
setting it to 0 wont create any issues?
How large can it grow?
Will it improve performance if its increased?

Thank you!
You need to increase cache-max-memory-size. The default is 512mb which is
fine for most workloads, but is too small for larger write volumes or
higher cardinality datasets. If you have lots of RAM you could set it to 0
to disable the limit and never get that error. You can also examine the
memBytes stat on cache measurement to get a sense of how big the caches are
in memory once the limit is raised.
"cache-snapshot-memory-size" shouldn't be changed. Increasing it causes
the cache in memory to be larger, which slows down snapshot compactions and
increases startup time.
The aborted compactions messages are informational and can be ignored. We
will probably move those to trace level logging: https://github.com/
influxdata/influxdb/issues/7425
Post by Dmitriy Akulov
Hello, I dont completely understand what this error means. "write failed
for shard 143: engine: cache maximum memory size exceeded"
The server has 128GB of RAM and the config has default settings.
As far as I understand the "cache-max-memory-size" and
"cache-snapshot-memory-size" parameters are not related to RAM.
What exactly do they do? How they should be configured? Based on incoming
data? Based on RAM?
What should I do to fix this?
Also what exactly this message means "aborted level 1 group (0).
compaction in progress"?
Log that contains both errors https://gist.githubusercontent
.com/jimaek/5f7fe91cc5f689273bed64401e564db1/raw/5aea6861548
a2f3d86940000f25576402bca29f5/gistfile1.txt
Thank you
--
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
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit https://groups.google.com/d/ms
gid/influxdb/88679401-4e5b-4cee-9f20-80266333994f%40googlegroups.com
<https://groups.google.com/d/msgid/influxdb/88679401-4e5b-4cee-9f20-80266333994f%40googlegroups.com?utm_medium=email&utm_source=footer>
.
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 a topic in the
Google Groups "InfluxDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/influxdb/vy1uhSsW7fw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
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/CALGqCvNycHt1eBV95-JjpFb-DwE95Gps9rpKQgr9pR6sfp9Ang%
40mail.gmail.com
<https://groups.google.com/d/msgid/influxdb/CALGqCvNycHt1eBV95-JjpFb-DwE95Gps9rpKQgr9pR6sfp9Ang%40mail.gmail.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
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 influxdb+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
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/CACMxjo5PGZcL1YaF47waO%3D1kgizgLKpC2w2S%2BvHe13er2aYA4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Loading...