Well it's recovered now after about 25 minutes of cycling through that shard but it was dicey there for a minute....
On Monday, 9 January 2017 14:29:29 UTC, Paul Seymour wrote: > > Turns out the OOM killer was kicking in on these. I have increased the > memory to 32gb on the servers but it's cycling around this shard for over > 15 minutes now. > > This particular DB is 150gb in size. This shard is only 5.5gb in size > > 5.5G 889 > > > > On Monday, 9 January 2017 13:51:00 UTC, Paul Seymour wrote: >> >> Hello, >> >> Running v1.1.0 on CentOS 7 and following a config change (to disable >> query logging) and restart now getting this:- >> >> 13:40:50 write failed for shard 889: engine: cache-max-memory-size >> exceeded: (1074008687/1073741824) >> >> Amongst many others and then Influx restarts and goes through it all >> again. >> >> Any ideas how I can recover this ? >> >> Thanks >> Paul >> > -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" 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/0adf2bdc-38e1-47d9-9fd7-ead356015483%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
