HDDS-1881. Design doc: decommissioning in Ozone #1196
Merged
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
hadoop-yetus
reviewed
Aug 1, 2019
|
|
||
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | |
hadoop-yetus
reviewed
Aug 1, 2019
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | | ||
| STALE + DEAD + DECOMMISSIONED | | |
|
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
reviewed
Aug 1, 2019
|
|
||
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | |
hadoop-yetus
reviewed
Aug 1, 2019
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | | ||
| STALE + DEAD + DECOMMISSIONED | | |
|
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
reviewed
Aug 8, 2019
|
|
||
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | |
hadoop-yetus
reviewed
Aug 8, 2019
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | | ||
| STALE + DEAD + DECOMMISSIONED | | |
|
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
reviewed
Aug 8, 2019
|
|
||
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | |
hadoop-yetus
reviewed
Aug 8, 2019
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | | ||
| STALE + DEAD + DECOMMISSIONED | | |
|
💔 -1 overall
This message was automatically generated. |
|
|
||
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | |
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | | ||
| STALE + DEAD + DECOMMISSIONED | | |
|
💔 -1 overall
This message was automatically generated. |
|
|
||
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | |
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | | ||
| STALE + DEAD + DECOMMISSIONED | | |
|
💔 -1 overall
This message was automatically generated. |
|
|
||
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | |
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | | ||
| STALE + DEAD + DECOMMISSIONED | | |
|
💔 -1 overall
This message was automatically generated. |
|
|
||
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | |
| Node state | Variable (# of containers) | | ||
| --------------------------------------|---------------------------------| | ||
| HEALTHY | `healthy` | | ||
| STALE + DEAD + DECOMMISSIONED | | |
|
💔 -1 overall
This message was automatically generated. |
anuengineer
approved these changes
Aug 28, 2019
|
|
||
| The second kind is when the failure is 'transient.' The user knows that this failure is temporary and cluster in most cases can safely ignore this issue. However, if the transient failures are going to cause a failure of availability; then the user would like the Ozone to take appropriate actions to address it. An example of this case, is if the user put 3 data nodes into maintenance mode and switched them off. | ||
|
|
||
| The transient failure can violate the availability guarantees of Ozone; Since the user is telling us not to take corrective actions. Many times, the user does not understand the impact on availability while asking Ozone to ignore the failure. |
amahussein
pushed a commit
to amahussein/hadoop
that referenced
this pull request
Oct 29, 2019
* Address comments from Anu * In-flight calculation is removed from the base model * Throttling is mentioned but will be discussed in a separated document * Model is improved to handle the over-replication in a specific way (to handle Nanda's use-case) * Stop conditions are defined independently from the model * Style of the table fragments are improved * typo fix (thx to sodonnell) * remove white spaces from the end of the lines * example is restored * minor whitespace improvement to support pdf conversion
RogPodge
pushed a commit
to RogPodge/hadoop
that referenced
this pull request
Mar 25, 2020
* Address comments from Anu * In-flight calculation is removed from the base model * Throttling is mentioned but will be discussed in a separated document * Model is improved to handle the over-replication in a specific way (to handle Nanda's use-case) * Stop conditions are defined independently from the model * Style of the table fragments are improved * typo fix (thx to sodonnell) * remove white spaces from the end of the lines * example is restored * minor whitespace improvement to support pdf conversion
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Design doc can be attached to the documentation. In this jira the design doc will be attached and merged to the documentation page.
See: https://issues.apache.org/jira/browse/HDDS-1881