cockroachdb / cockroachdb/cockroach
add support for clearing the recently decommissioned nodes table
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
A customer is planning on repaving their cluster at a regular interval, a process which involves decommissioning nodes. This table becomes noise to them since they want to do this every month. They would like to know how long the data lives in this view and if there is an easy way to clear the table.
We have noticed that this is actually a bug in the UI. We should be surfacing recently decommissioned nodes in a separate table in the overview page, instead of in the main Nodes table. As Marylia pointed out, this issue is most likely caused by a difference in the name of the status for a node between version upgrades.
As far as the customer is concerned, they are temporarily getting around this by detaching the data drive rather than performing a full repave.
Jira issue: CRDB-28924
gz#17743
Contributor guide
Assessment
This issue has not been assessed yet.