-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restarting influxdb overwrites default shardspace config #886
Comments
Same happens to me even without restarting influx and without having graphite. |
Yeah I think it is unrelated to, just much easier to repeat under load. I "fixed" it by just leaving default shardspace and adding ones I wanted on top of it |
If you send writes to a non-existant database, the graphite plugin will create it. If you create a database and have no shard spaces created, it will create a default one for you. I think the solution here is simple. Create the database AND your shard spaces before writing any data to InfluxDB. Is this not an option? |
It does not create database in 0.8, it does complain in logs that there is no database ;] And I did that. Turned off graphite plugin, created DB, turned plugin back on. Result ? Ok at first, after restarting database this happened: original parameters for shard creation in https://gist.github.com/XANi/b22ad3d1174bdc851281 2 database, method of doing that was a bit different:
Only way I managed to make it work is:
|
I think I can reproduce this. Will be looking into it today |
Fixes #886. Shard spaces would not have compiled regexes when the server is restarted and the cluster config is pulled from a raft snapshot. A call to MatchSeries would then reset the regex for the shard space. BAAAAAD.
This will help users recover from #886. It's dangerous functionality because it only changes the metadata. Will document and tell people to use with caution.
Fixes #886. Shard spaces would not have compiled regexes when the server is restarted and the cluster config is pulled from a raft snapshot. A call to MatchSeries would then reset the regex for the shard space. BAAAAAD.
This will help users recover from #886. It's dangerous functionality because it only changes the metadata. Will document and tell people to use with caution.
Fixed in 0.8.2 with this commit 64eedb7 |
Fixes #886. Shard spaces would not have compiled regexes when the server is restarted and the cluster config is pulled from a raft snapshot. A call to MatchSeries would then reset the regex for the shard space. BAAAAAD.
This will help users recover from #886. It's dangerous functionality because it only changes the metadata. Will document and tell people to use with caution.
If graphite plugin is active while creating DB it messes up shardspaces(v0.8.0).
My shardspace config: https://gist.github.com/XANi/b22ad3d1174bdc851281
Example: 2 node cluster; graphite plugin set up to write into "stats" database
results in
after I change to write to 'stat' database, restart nodes and start writing, it okay... but after restarting one node other database's shardspace get messed up too:
So it looks to me like:
The text was updated successfully, but these errors were encountered: