Skip to content

HDDS-14682. Unify OzoneManagerProtocolPB failover proxy provider#9929

Open
ivandika3 wants to merge 5 commits intoapache:masterfrom
ivandika3:HDDS-14682
Open

HDDS-14682. Unify OzoneManagerProtocolPB failover proxy provider#9929
ivandika3 wants to merge 5 commits intoapache:masterfrom
ivandika3:HDDS-14682

Conversation

@ivandika3
Copy link
Contributor

@ivandika3 ivandika3 commented Mar 15, 2026

What changes were proposed in this pull request?

Since HadoopRpcOMFollowerReadFailoverProxyProvider should be able to support both OM follower and OM leader request flows, we can always use HadoopRpcOMFollowerReadFailoverProxyProvider for the OzoneManagerProtocolPB failover proxy provider. This will unify some of the implementations such as the client read consistency implementation in HDDS-14509.

This means that HadoopRpcOMFailoverProxyProvider is only used for other OM non-OzoneManagerProtocolPB protocols (e.g. OMAdminProtocolPB).

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-14682

How was this patch tested?

Existing CI (Clean CI: https://github.com/ivandika3/ozone/actions/runs/23105516389)

The unified HadoopRpcOMFollowerReadFailoverProxyProvider hardcoded
useFollowerRead=true, ignoring ozone.client.follower.read.enabled
(default false). This forced all read-eligible requests through the
LINEARIZABLE_ALLOW_FOLLOWER server path instead of DEFAULT, causing
test timeouts due to the different Ratis execution flow.

Pass the config value through the constructor so follower read
behavior matches the configuration.

Made-with: Cursor
@ivandika3 ivandika3 self-assigned this Mar 15, 2026
@ivandika3 ivandika3 marked this pull request as ready for review March 15, 2026 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant