A very happy InfluxDB user here, but did you really had to title your release email "InfluxDB 1.0 GA is Here! Plus 27x Faster than MongoDB Benchmarks"?
InfluxDB 1.0 GA Released: A Retrospective and What’s Next
11–20 of 83 posts
Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next
#12Cool to see a database specializing in time series data.
Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next
#13Earlier quoted context omitted.
Or maybe you were sad because you only saw package downloads from S3 and you were looking for an actual Debian repository? Well, that actually already exists. See: https://docs.influxdata.com/influxdb/v1.0/introduction/insta...
I'm glad you answered your own question, but it was you who asked that. I couldn't care less if they provided APT repository; using random repositories from various companies is asking for trouble with managing your servers (hint: package retention policies).
I answered my own question because your original comment left no clue as to why you're so upset. Neither does this one that I'm now responding to.
Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next
#14We've been using influx since 0.9 in production. Had a few bumps with cardinality growing out of control, but now working around those limits, it's going well. Looking forward to that being something tackled with upcoming releases.
Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next
#15We've been using influx since 0.9 in production. Had a few bumps with cardinality growing out of control, but now working around those limits, it's going well. Looking forward to that being something tackled with upcoming releases.
Yep, we're very focused on solving the cardinality problem now. See these for some details about how we're thinking about it:
https://github.com/influxdata/influxdb/pull/7175 https://github.com/influxdata/influxdb/pull/7174 https://github.com/influxdata/influxdb/pull/7186 https://github.com/influxdata/influxdb/pull/7264
Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next
#16Earlier quoted context omitted.
I'm glad you answered your own question, but it was you who asked that. I couldn't care less if they provided APT repository; using random repositories from various companies is asking for trouble with managing your servers (hint: package retention policies).
I answered my own question because your original comment left no clue as to why you're so upset. Neither does this one that I'm now responding to.
Agreed, them providing .debs is far from "packaging being a mess". I'm quite happy that they provided .debs, worked with them to make some changes to the debs via pull-requests, and after that have been super happy with the packaging. I grab and import their packages into my own private repo for historic reasons, but it does mean I have to chase upstream changes. Personally, I think this is a straw-man argument. With many places not even providing packages, I'm glad that the Influx folks went through that process for me.
Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next
#17Packages built in the same shitty way as always. I expected nothing less from you guys.
We're happy to take PRs. Seems everyone has opinions on packaging and you know what it's like when everyone has opinions, right? :)
> Seems everyone has opinions on packaging and you know what it's like when everyone has opinions, right? :)
Don't try to push this into opinion realm, because it's not, it's a standards realm. Your package doesn't stand lintian test, and it's not a doesn't-really-matter type of errors that there's no README or license file. You don't even put an initscript in packages in a proper way.
It wouldn't matter that much, but your build system doesn't have an easy, clean build from local source tree with a method of putting files in right places in $DESTDIR, so the software could be properly debianized (or equivalent) by somebody else.
Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next
#18I've been using InfluxDB for almost a year now. At one point around 9 months ago I had given up on it because it was a bit crashy, and the database just was growing too fast. But the promise behind it was too compelling and I started experimenting with newer versions around 6 months ago and it has been just great! Much easier to deal with than Graphite/collectd/carbon, telegraf has not been eating our servers like collectd was, CPU usage is way down... Loving InfluxDB. Still need to implement annotations and SNMP polling in telegraf, but it is awesome. We are even pushing some application stats into it.
Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next
#19Influx is absolutely amazing. We're using it along with grafana to store and display our desktop and web apps' analytics (it completely replaced GA), store and display HTTP health analytics (piping custom uwsgi request logger into UDP input), and do continuous analysis of Hearthstone games.
It's incredibly fast and the grafana/influx/telegraf stack is really cool to play with. Highly recommended.
Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next
#20I've been using InfluxDB for almost a year now. At one point around 9 months ago I had given up on it because it was a bit crashy, and the database just was growing too fast. But the promise behind it was too compelling and I started experimenting with newer versions around 6 months ago and it has been just great! Much easier to deal with than Graphite/collectd/carbon, telegraf has not been eating our servers like co…
We updated the SNMP plugin a few weeks ago. Was thanks to a contributor who has been super helpful. Does the updated one do what you need?