[GitHub] [ozone] sodonnel commented on pull request #4154: HDDS-7738. SCM terminates when adding container to a closed pipeline

[GitBox <gi...@apache.org>]

sodonnel commented on PR #4154:
URL: https://github.com/apache/ozone/pull/4154#issuecomment-1374230304

   Does the SCM terminate on the active SCM, or is this on the follower SCMs?
   
   If we allow an open container on a closed pipeline, what will close the open container? The normal close flow is triggered when either the container fills up and the DN triggers a close, or the pipeline is closed and it triggers a close to all containers on the pipeline.
   
   I am also wondering, what happens to a container which is allocated on SCM, but never gets anything written to it. It will never get replicas on a DN, and hence will never have any replicas reported. Will it get cleaned up or will it hang around forever?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org