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

[Update] Document behavior of DROP DATABASE on multi-node #692

Open
erimatnor opened this issue Mar 29, 2021 · 0 comments
Open

[Update] Document behavior of DROP DATABASE on multi-node #692

erimatnor opened this issue Mar 29, 2021 · 0 comments
Labels
multinode Multinode-related content

Comments

@erimatnor
Copy link
Contributor

When dropping a distributed database, the corresponding databases are not dropped on the data nodes. This is to prevent accidentally dropping data that should be preserved on those nodes. Further, since the databases could have existed prior to incorporating them into a multi-node cluster, they might have had data prior to being part of a distributed database.

However, keeping the database on a data node instance prevents adding them back. The databases either have to be dropped manually on each data node or the dist_uuid removed in the metadata on each data node DB.

Until we have a more seamless solution for how to handle this, we should document the current behavior and describe how to "add back" a data node using the same database.

@erimatnor erimatnor added the multinode Multinode-related content label Mar 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
multinode Multinode-related content
Projects
None yet
Development

No branches or pull requests

1 participant