Project

General

Profile

Feature #9671

Allow crush node trees to be fully traversable after a bucket delete

Added by Christina Meno almost 7 years ago. Updated almost 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Backend (REST API)
Target version:
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:

Description

Currently DELETE on
cluster/<fsid>/crush_node/<node_id>

will delete any valid node just as the CLI allows
It does not re-parent the children of the deleted node.

It seems that it would cause issue when a higher level bucket gets deleted say root, region, datacenter, etc

There are two approaches that come to mind that would improve this:
1. re-parent child nodes

2. refuse to delete nodes that have children
allowing this endpoint to take query_parameters recursive and force

History

#1 Updated by Christina Meno almost 7 years ago

  • Status changed from New to Rejected

#2 Updated by Dan Mick almost 7 years ago

Reason for rejection?...(for the record)

#3 Updated by Christina Meno almost 7 years ago

  • Target version changed from 1.3 backlog to 1.3-dev7

Also available in: Atom PDF