IMHO if your volume is not in 300K data points per second, there is still plain old PostgreSQL, which is perfectly suitable for storing time-series and is time-tested and very reliable, allowing you to keep your TS data alongside your other (business) data so that you can analyze it all together without having to extract out of unfamiliar storage. I've hacked a project which demonstrates how it can be done, see <a href="https://github.com/grisha/timeriver" rel="nofollow">https://github.com/grisha/timeriver</a> and my blog explaining the technique <a href="http://grisha.org/blog/2015/09/23/storing-time-series-in-postgresql-efficiently/" rel="nofollow">http://grisha.org/blog/2015/09/23/storing-time-series-in-pos...</a>
So, we were using InfluxDB on v0.8.x but had two data corruption incidents. Both times I tried the recovery utilities with no luck. Even with some data loss, it was time to move to another db.<p>We were only getting ~1k tps with some spikes of 10k tps. I hope for the rest of the users, there was some work done of that front. Maybe in the future we will revisit out of curiosity, since we have no issues at the moment.