Xushaohong commented on code in PR #4128:
URL: https://github.com/apache/ozone/pull/4128#discussion_r1067670568
##########
hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/OmUtils.java:
##########
@@ -277,6 +277,7 @@ public static boolean isReadOnly(
// Although indirectly the Ranger sync service task could invoke write
// operation SetRangerServiceVersion.
case GetKeyInfo:
+ case TransferLeadership:
Review Comment:
Just to clarify: The transferLeadershipRequest is a read request while the
setConfigurationRequest is a write request (From Ratis code).
We need to send setConfigurationRequest and then transferLeadershipRequest
to Ratis server in sequence, so the question from Sammi is meaningful.
I think the reason why we should still keep it as a READ operation for OM
@ChenSammi
1. Just like @symious said, the write request would be sent to all 3 OMs
2. The transfer Leadership process will not write to OM's DB, the state
change is on the Ratis level, whose action is guaranteed by the ratis. Could
refer to **RangerBGSync** above, which also does not write to OM's db.
--
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]
