[candiddevmike]

What a ride. You're close to releasing Influx 2.0 without a clear migration strategy for your customers, and then you think it's a good idea to announce yet another storage rewrite? Why should customers stick with you guys when you have a track record for shipping half baked software, rewriting it, and leaving people out in the cold?

[pauldix]

Users of InfluxDB 1.x can upgrade to 2.0 today. It's an in-place upgrade and just requires a quick command to make it work. Further, InfluxDB 2.0 also has the API for InfluxDB 1.x. We've been putting out InfluxDB 1.x releases while we've been developing 2.0. One of the reasons we waited so long to finalize GA for 2.0 was because we had to make sure there was a clean migration path and there is.

For our cloud 1 customers, they'll be able to upgrade to our cloud 2 offering, but in the meantime, their existing installations get the same 24x7 coverage and service we've been providing for years.

As for how this will be deployed, it will be a seamless transition for our cloud customers when we do so. Data, monitoring and analytics companies replace their backend data planes multiple times over the course of their lifetime.

For our Enterprise customers, we'll provide an upgrade path, but not until this product is mature enough to ship an on-premise binary that won't get a chance to get upgraded but for a few times a year.

The only difference here is that we're doing it as open source. They always do theirs behind closed doors. I'm sure most of our users and many of our customers prefer our open source approach.

[toinbis]

That is a rude comment. Why have you sticked with windows or mac os when they released 20 versions of their software? NT and 98, windows server, etc.? Because it does it's job, who cares that there are other versions that also works! I run influx stack in production for two years and had (almost) zero problems with it. Everything works, is being maintained and on the side the new cool stuff is being rolled out, what's the problem with that? Paul, as a happy user of influx, let me say - thank you guys for what you are creating!

[pauldix]

Thanks :)

[mhall119]

InfluxDB 1.x user can upgrade to InfluxDB 2.0 pretty easily, there is an `upgrade` command that will convert your metadata from 1.x to 2.0.

Your time series data doesn't even need to be touched, it'll "just work" after the upgrade.

[candiddevmike]

This is different than the previous `influxd migrate` command that never seemed to work, right?

[mhall119]

For a while the 2.0 development branch was using a different storage file format than 1.x, which required migrating your time series data.

But by the 2.0 Release Candidate that was reverted so that it will use the same file format as 1.x, and the 2.0 functionality was backported onto that, so the upgrade path for 1.x to 2.0 is much simpler now than it was going to be.

[alsargent]

Migration is something we feel is very important, which is why we've delivered a single-CLI-command upgrade from 1.x to 2.0. Here's the documentation: https://docs.influxdata.com/influxdb/v2.0/reference/upgradin...

[alsargent]

(InfluxDB employee here. Sorry I should have mentioned that in my original post.)

[avthar]

If you're an InfluxDB user looking to migrate to a more reliable and solid database, here's a tool [1] that allows you to do that in a single command:

[1]: https://www.outfluxdata.com

[deathtrader666]

It would've been better if you explicitly disclosed your employment at TimescaleDB.

[avthar]

Apologies, I did so elsewhere in the thread. I work at Timescale!