Last Monday we upgraded our Influxdb server from v0.13 to v1.0. Since then
we have had nothing but problems. At first, I thought it was due to the
series cardinality of our database, which I measured at around 122,000. So,
I modified the schema a little and started rebuilding a new database. It
didn't help: My cardinality is only around 2800 and I have a lot less
records and I am still getting the problem.
Basically, my application server reads files from which it creates
measurement points, which it then writes to Influx. After only 20 minutes
or so, I see write timeouts both from my application and from influx
("failed to store statistics timeout").
Nothing but the version of Influx has changed, so I have to assume that
v1.0 is at fault.
Server has 5 cores, 7.82GB and runs Debian 8.5 (Jessie).
Can anyone offer any advice?
--
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/CAGZfoMrEdQjVCe6WkHPWf-dECbtuW9q-GA8HAdcvxQ880Xb-Qg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
