Sumit Agrawal created HDDS-8229:
-----------------------------------
Summary: SCM stalenode handle mark pipeline as Readonly instead of
closure
Key: HDDS-8229
URL: https://issues.apache.org/jira/browse/HDDS-8229
Project: Apache Ozone
Issue Type: Sub-task
Reporter: Sumit Agrawal
In big cluster, if one of DN do not respond within 5min, due to slow running or
other cases,
* SCM will mark it as stale and closes pipeline and all containers
* If DN response is received, again SCM will create all pipeline and cotainers
This creates lot of event, extra burden over SCM and DN.
Other impact:
* Few created container remains empty or small container
To handle the ripple effect of closure of pipeline and containers and
re-creation,
* Can mark pipeline as readonly, i.e. it will not be used further for any new
block allocation
* Containers/pipeline will remain open, till either DN becomes healthy, or DN
is dead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]