Stephen O'Donnell created HDDS-9151:
---------------------------------------
Summary: Close EC Pipeline when container transitions to closing
Key: HDDS-9151
URL: https://issues.apache.org/jira/browse/HDDS-9151
Project: Apache Ozone
Issue Type: Sub-task
Reporter: Stephen O'Donnell
In testing we have found an issues in the ECWritableContainerProvider.
For EC a pipeline is used for only one container, when the container gets
closed, the pipeline also gets closed. However closing the container can take
some time. First it is marked as CLOSING in SCM, then SCM sends commands to the
DNs to close it, and finally the container gets CLOSED.
As we limit the number of pipelines in SCM, containers in a CLOSING state mean
there are containers/pipelines which are effectively closed, but the pipeline
are still counted toward the limit.
Ideally, when a container transitions to CLOSING in SCM, if the container is an
EC container, we should also close the associated pipeline to avoid it counting
toward the limit.
This could be achieved relatively simply inside the
PipelineManagerImpl.removeContainersFromPipeline() method which is called as
soon as the container transitions to CLOSING via
ContainerStateManagerImpl.updateContainerState() when it executes the
containerStateChangeActions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
