InfluxDB v0.9.0 release update
This is an update to the v0.9.0 release plan I posted a month ago. The short answer is: it’s not released or ready yet, but we’re making great progress. We would rather disappoint you on a release date than disappoint you with sub-par software.
There are only three items from that list that we still have to finish:
- Data nodes can get shards that have been truncated
- Replacing a downed node
- Write back-pressure if data nodes are falling behind on replication
We’ve decided to add a few features to that list:
The first three of these new features are important for the new API to hit important use cases for InfluxDB users. The last one on selecting tag names is a usability enhancement based on many people finding it counter-intuitive that they can’t select tag names. Currently, you can get tag names by putting them in the
GROUP BY clause.
We’re making great progress and moving things forward every day. Clustering has improved dramatically over the last few weeks alone. Last month we merged 153 PRs. You can see from the CHANGELOG that there have been many bug fixes and features. We still have some bug fixes on continuous queries and more clustering work and testing, but it’s continuously improving.
For the underlying data store, we don’t anticipate making any more breaking changes in the 0.9.0 release cycle. That means that you should be able to upgrade from one RC to another from this point and still keep your data around. However, beware that if we need to make a breaking change, we will. We just don’t have anything on the open list that would cause that so we don’t anticipate it happening.
I’m hesitant to offer delivery guarantees since this release is obviously lagging far behind what we had originally hoped for. I’ve updated the front page to say “coming soon”. However, we’re aiming to have those features done no later than May 31st. We’ll also be fixing bugs as they appear from people testing out the 0.9.0 RCs. The official release won’t happen until we hit feature freeze and have extensive soak testing done. That means the full release won’t be until sometime after feature complete date since we’ll have to do a month of soak testing against whatever RC becomes the final release.
The current batch of RCs aren’t truly release candidates. The first one that will be a true release candidate will be after those features are done and any show stopper bugs have been fixed. There are reasons we made them RCs, but we’ll be changing that on the next major release. I’ll be announcing the RC build number that is feature complete on this blog as soon as it’s available. However, if you’re developing a new project, the current 0.9.0 RCs are what you’re best developing against. We’ll continue to release those regularly as we fix bugs and add these last features.
For everyone that has been eagerly awaiting this release, I apologize for yet another delay. I’m sure it’s painful for you and it’s definitely painful for us. However, we aren’t going to cut this release until we have these key features and have done extensive testing to have confidence that it is reliable, robust, recoverable, and truly production worthy.
For those wanting to pitch in, testing on new RCs (particularly clusters under load) is very helpful. Also, we’re actively taking PRs from the community and we’re hiring. We’ve had a number of contributors roll up their sleeves over the last few months and that seems to be picking up. Thank you to everyone in the community for contributing and for those of you giving us encouragement.
From this point on I’ll post an update on our progress every two weeks until 0.9.0 is released. I’ll highlight community contributions and talk about the high level things from the CHANGELOG.