Skip to content
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

influx_inspect deletetsm : targeting all shards fails using wildcard when some *.tsm is missing #10133

Closed
sinmki opened this issue Jul 26, 2018 · 2 comments

Comments

@sinmki
Copy link

sinmki commented Jul 26, 2018

Bug report

System info: master on 25-July-2018 (v1.6) , 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux

Steps to reproduce:

Have multiple shards where some do not contain a *.tsm-file.

Delete a specific measurement from all shards for a database using a wildcard :
influx_inspect deletetsm -v -measurement "m" data/db/autogen/*/*.tsm

Expected behavior:
All measurements in the *.tsm-files from all shards get deleted.

Actual behavior:
Measurement still exists in shards following after the shard that's lacking a *.tsm.

Tested multiple times. It is required to manually proceed the deletetsm by guiding the right shard ID that's following the shard that's missing a *.tsm e.g.
influx_inspect deletetsm -v -measurement "m" data/db/autogen/108*/*.tsm
Until it again stops by possibly missing another *.tsm.

@stale
Copy link

stale bot commented Jul 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 24, 2019
@stale
Copy link

stale bot commented Jul 31, 2019

This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.

@stale stale bot closed this as completed Jul 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants