You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "smengcl (via GitHub)" <gi...@apache.org> on 2023/03/21 23:43:30 UTC

[GitHub] [ozone] smengcl commented on pull request #4423: HDDS-8205. Reorder OM nodes in HA acceptance tests

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

   > Thanks @smengcl for the review. I think failover logic keeps track of leader for cases where client is not thrown away:
   > 
   > https://github.com/apache/ozone/blob/a76fb0ee586699baad817a928db1580e760a6df9/hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/om/ha/OMFailoverProxyProviderBase.java#L174-L192
   
   Thanks @adoroszlai for the pointer. Though I presume in the case of invoking CLI commands one after another, the second command and so on would still resort to checking the first OM in the config, then failover over to the leader (with the leader node info provided in the response) if the first OM is not the leader? The client could write some temp file under `/run` or `/tmp` so it persists across different JVM launches.


-- 
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