adwetojha commented on code in PR #11752:
URL: https://github.com/apache/ozone/pull/11752#discussion_r4388498967
##########
hadoop-hdds/common/src/main/java/org/apache/hadoop/ozone/ClientVersion.java:
##########
@@ -42,6 +42,9 @@ public enum ClientVersion implements ComponentVersion {
"This client version has support for Object Store and File " +
"System Optimized Bucket Layouts."),
+ KEY_ALLOCATION_PIPELINE_NOT_FOUND(4,
Review Comment:
Thanks for pointing this out! I've removed the client version bump and
reused KEY_ALLOCATION_ERROR as suggested. Added regression coverage confirming
that v3 clients can still use OBS/FSO CreateKey.
One compatibility concern I wanted to check with you: older OM versions
historically emitted KEY_ALLOCATION_ERROR for broader failures, so a new client
connecting to such a server could retry an unrelated failure for up to 90
retries.
Would you consider this tradeoff acceptable, or would you prefer a different
way to distinguish the transient pipeline failure?
--
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]
