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

[0.10.0] DROP DATABASE does not work in a cluster #5612

Closed
e-dard opened this issue Feb 10, 2016 · 0 comments
Closed

[0.10.0] DROP DATABASE does not work in a cluster #5612

e-dard opened this issue Feb 10, 2016 · 0 comments
Assignees
Milestone

Comments

@e-dard
Copy link
Contributor

e-dard commented Feb 10, 2016

On a 3-node fully replicated cluster create a database on a node, and then make a write on that node. Finally, call DROP DATABASE db.

Expected result:

  • The database information should be deleted from the meta store, and also all files wiped from each data node.

Actual result:

  • The meta store is updated, but files are only removed on the the node where the DROP DATABASE command occurred.
@rossmcdonald rossmcdonald added this to the 0.11.0 milestone Feb 10, 2016
@e-dard e-dard self-assigned this Feb 16, 2016
e-dard added a commit that referenced this issue Feb 22, 2016
Fixes #5612, #5573 and #5518.

Using the MetaExecuter, queries that need to run on both data nodes
and optionally the meta store will be executed across all data nodes
in the cluster.
dgnorton pushed a commit that referenced this issue Feb 23, 2016
Fixes #5612, #5573 and #5518.

Using the MetaExecuter, queries that need to run on both data nodes
and optionally the meta store will be executed across all data nodes
in the cluster.
dgnorton pushed a commit that referenced this issue Feb 24, 2016
Fixes #5612, #5573 and #5518.

Using the MetaExecuter, queries that need to run on both data nodes
and optionally the meta store will be executed across all data nodes
in the cluster.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants