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

DROP SHARD doesn't remove data from _internal #6988

Closed
beckettsean opened this issue Jul 8, 2016 · 2 comments
Closed

DROP SHARD doesn't remove data from _internal #6988

beckettsean opened this issue Jul 8, 2016 · 2 comments

Comments

@beckettsean
Copy link
Contributor

Bug report

System info:
InfluxDB 0.13

Steps to reproduce:

> drop shard 257
> SELECT "writePointsOk",id  FROM "_internal".."shard" WHERE time > now() - 10s group BY *
name: shard
tags: clusterID=36934674580451795, database=_internal, engine=tsm1, hostname=sean-stable, id=252, nodeID=0, path=/var/lib/influxdb/data/_internal/monitor/252, retentionPolicy=monitor
time            writePointsOk   id
----            -------------   --
1468005095000000000 317511      252

<snip>

name: shard
tags: clusterID=36934674580451795, database=mydb, engine=tsm1, hostname=sean-stable, id=257, nodeID=0, path=/var/lib/influxdb/data/mydb/default/257, retentionPolicy=default
time            writePointsOk   id
----            -------------   --
1468005095000000000 1       257

<snip>
> 

(The shard only had one point before being dropped, so that's consistent output)

Expected behavior:

Once dropped, the shard should not appear in _internal monitoring. For shards removed by retention policy expiration things work as expected, but for manually dropped shards the data persists.

Actual behavior:

Statistics about shards that have been dropped by DROP SHARD persist in _internal

Additional info:

@beckettsean
Copy link
Contributor Author

@rkuchan, nice catch

@jsternberg is in the midst of a PR that should resolve this.

@jsternberg
Copy link
Contributor

This should be fixed with #6964. If this is still an issue with that fix, please reopen so I can take another look and address the problem.

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

2 participants