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

server: option to obliterate decommissioned nodes from cluster memory #33542

Open
couchand opened this Issue Jan 7, 2019 · 1 comment

Comments

2 participants
@couchand
Copy link
Collaborator

couchand commented Jan 7, 2019

Use Case to support remove option to clear decommissioned nodes from UI/DB (not dead node):
We are trying to use cockroachdb in the cloud, hosts will be replaced/refreshed every 30 days using Jenkins.
Running a cluster of 4 in 3 regions (Oregon, NOVA, Ohio) is at least 12 nodes per month accumulating under Decommissioned in prod.
We don't care about those nodes, they are gone forever.
Dev/test where we build rotation processes, is getting messy with all the decomms in the UI.
Recommendation: Build option to clear with time frame of how far back, let customer decide between info and clutter. Send a query that can purge decomms from the DB and it will be added to our decomm code.

Originally posted by @Timbo000002 in #24636 (comment)

@couchand

This comment has been minimized.

Copy link
Collaborator

couchand commented Jan 7, 2019

cc @tbg for triage

@tbg tbg changed the title Option to obliterate decommissioned nodes from cluster memory server: option to obliterate decommissioned nodes from cluster memory Jan 7, 2019

@tbg tbg added this to Incoming in Core Stability via automation Jan 7, 2019

@tbg tbg added the C-enhancement label Jan 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment