-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Conversion to tsm fails with exceeds max index value #5865
Comments
@pbooth it sounds like the TSM writer needs to deal with this condition as part of the conversion. @joelegasse will likely need to take a look, I think. |
@pbooth one thing you might try is to reduce the -sz parameter to the influx_tsm command to some smaller value. provided you hit the file size limit before you hit the index entries limit, you should avoid the condition that causes the conversion to barf. |
@pbooth Thank you for finding this. @jonseymour is right, we need to handle this in the conversion tool, and there's nothing you should need to do with your files. This is the side effect of a design decision in TSM, specifically the I should have a fix merged shortly, and we're planning a |
This should fix #5865 This commit also removes the dependecy on the influxql package constants that were used to write b1 and bz1 files and have changed since the release of 0.10
This should fix #5865 This commit also removes the dependecy on the influxql package constants that were used to write b1 and bz1 files and have changed since the release of 0.10
Hello, I have a 0.9.6 influxdb that I have upgraded to 0.10.1-1
When I try to upgrade the shard in a 30GB DB I get the following:
Is there something that I can with the bz shard to shrink it?
The text was updated successfully, but these errors were encountered: