ivandika3 commented on PR #5288: URL: https://github.com/apache/ozone/pull/5288#issuecomment-2035978794
Another observation is that the benchmark with writes will eventually converge to the leader, which makes most traffic to hit the leader eventually for persistent client (e.g. Ozone client in S3G). Example case 1: READ -> follower 1 2: WRITE -> follower 1 will throw NotLeaderException, redirect to leader 3: READ -> leader (until the leader fails) One possible way is to ensure READ is sent to the follower, is to modify the client (OmFailoverProxyProviderBase) keep track of the current leader and followers of the OM service. All the read requests will be sent to the follower, while the write requests will be sent to the leader. We might adapt some of the logic from HDFS's `ObserverReadProxyProvider`. -- 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]
