smengcl commented on PR #11700:
URL: https://github.com/apache/ozone/pull/11700#issuecomment-6360470589

   Thanks @Russole.
   
   > does this close-command path involve ReplicationManager?
   
   Yes, `ReplicationManager` sends the close command to the datanode here. 
`CloseContainerEventHandler` only moves the container to CLOSING right away. 
Its own close command waits for `ozone.scm.close.container.wait.duration` 
(default 150s, unset in this test). On each `ReplicationManager` run (every 1s 
here), `ClosingContainerHandler` calls 
`ReplicationManager#sendCloseContainerReplicaCommand` for CLOSING containers, 
and that is the command the datanode acts on. From CI log:
   
   ```
   11:32:56,524 [EventQueue-CloseContainerForCloseContainerEventHandler] Close 
container Event triggered for container : #3, current state: OPEN
   11:32:57,354 [ReplicationMonitor] ReplicationManager - Sending command 
[closeContainerCommand: ... containerID: 3, ...]
   ```


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to