HDDS-2196 Add CLI Commands and Protobuf messages to trigger decom states #17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…mpose .env files. Closes apache#1570.
…tis. Contributed by Tsz-wo Sze(apache#1517).
Signed-off-by: Anu Engineer <[email protected]>
Signed-off-by: Anu Engineer <[email protected]>
Signed-off-by: Anu Engineer <[email protected]>
Signed-off-by: Anu Engineer <[email protected]>
Contributed by kevin su.
…he read/write path (HDDS). (apache#1612)
commit 9d6a1b97f365b22392ceac8d958cf041c3515bd6 Author: Doroszlai, Attila <[email protected]> Date: Mon Oct 7 13:42:35 2019 +0200 HDDS-2265. integration.sh may report false negative Revert "HDDS-2217. Remove log4j and audit configuration from the docker-config files" This reverts commit 4b0a5bca465c84265b8305e001809fd1f986e8da.
…he read/write path. (apache#1633)
…Contributed by Xiaoyu Yao. (apache#1642)
…tAdditionalTokenIssuers (apache#1556)
…ecommission and maintenance commands to be sent from the CLI and update the node status in a skeleton decommission manager
cchenax
pushed a commit
to cchenax/ozone
that referenced
this pull request
May 18, 2021
tanvipenumudy
added a commit
to tanvipenumudy/ozone
that referenced
this pull request
May 12, 2022
# This is the 1st commit message: Initial Commit # This is the commit message apache#2: more slight changes # This is the commit message apache#3: changes++ # This is the commit message apache#4: getExecutorService Changes # This is the commit message apache#5: applyTransaction() Changes # This is the commit message apache#6: changes++ # This is the commit message apache#7: TestOzoneManagerLock changes # This is the commit message apache#8: add changes # This is the commit message apache#9: add more minor changes # This is the commit message apache#10: add config to ozone-default.xml # This is the commit message apache#11: minor changes # This is the commit message apache#12: change modulo logic # This is the commit message apache#13: changes # This is the commit message apache#14: changes++ # This is the commit message apache#15: add changes++ # This is the commit message apache#16: minor changes # This is the commit message apache#17: Changes (to be reverted) # This is the commit message apache#18: Changes 09/05
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
16 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change provides 3 new CLI commands:
To allow for cases where many DNs are on the same host, the hostname can also have a port appended, eg:
These commands make use of 3 new protobuf messages, defined in StorageContainerLocationProtocol:
All 3 accept a list of strings (for hostnames) and the maintenance message also allows an int to specify the end time in hours.
These 3 commands make a call to a new class NodeDecommissionManager which takes the list of hosts and validates them. If any host is invalid or not part of the cluster, the entire command is failed and the CLI will show an error. Assuming the validation passes OK, the list of nodes will be switch into DECOMMISSIONING, ENTERING_MAINTENANCE or back into IN_SERVICE.
At this point in time, there is no decommission logic present, the nodes will simply remain in the interm state forever. The actual decommissioning logic will be added in a further Jira.