HDDS-13579. [Docs] Explain how Ratis write pipelines are calculated #9580
+58
−0
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
jojochuang
requested review from
ashishkumar50,
siddhantsangwan,
sodonnel,
sumitagrawl and
szetszwo
Contributor
|
@jojochuang , thanks for working on this! Could you limit the line length to 120 characters like the code? It is easier to comment on it. |
Discovered and corrected the documentation for how the number of EC pipelines is calculated. The previous analysis was incorrect. - `ErasureCoding.md` is updated to describe the two new properties `ozone.scm.ec.pipeline.minimum` and `ozone.scm.ec.pipeline.per.volume.factor` and the `max()` logic used to determine the target number of pipelines. - `ProductionDeployment.md` is updated to reference the correct and existing configuration property for tuning EC pipelines. Change-Id: I393dc60d8745da2b2bb7899530665a108956446d
Change-Id: I0ec667c21155436eb6a0654782b43b48636f75d5
Contributor
Author
|
thanks for review. updated. |
Contributor
ashishkumar50
left a comment
ashishkumar50
left a comment
There was a problem hiding this comment.
@jojochuang Thanks for writing this up.
| recommended, as it allows the cluster to scale pipeline capacity naturally with its resources. You can use the | ||
| global limit (`ozone.scm.ratis.pipeline.limit`) as a safety cap if needed. A good starting value for | ||
| `ozone.scm.pipeline.per.metadata.disk` is **2**. Monitor the `NumOpenPipelines` metric in SCM to see if the | ||
| actual number of pipelines aligns with your configured targets. |
Contributor
There was a problem hiding this comment.
I think NumOpenPipelines metrics doesn't exist. We can either use admin command to see number of open pipelines or may use recon as well to see the open pipelines.
Contributor
Author
There was a problem hiding this comment.
To clarify, the SCM web UI has a section Pipeline Statistics, and it pulls the metrics from:
{
"name": "Hadoop:service=SCMPipelineManager,name=SCMPipelineManagerInfo",
"modelerType": "org.apache.hadoop.hdds.scm.pipeline.PipelineManagerImpl",
"PipelineInfo": [
{
"key": "CLOSED",
"value": 0
},
{
"key": "ALLOCATED",
"value": 0
},
{
"key": "OPEN",
"value": 1
},
{
"key": "DORMANT",
"value": 0
}
]
},
Change-Id: I2537905761cf45d23cdb3701b2f0c94e7ff2485a
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
What changes were proposed in this pull request?
HDDS-13579. [Docs] Explain how Ratis write pipelines are calculated
Please describe your PR in detail:
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-13579
How was this patch tested?
Doc only.