[ https://issues.apache.org/jira/browse/HDFS-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik Krogen updated HDFS-13779: ------------------------------- Status: Patch Available (was: In Progress) Attached v000 patch based on recent changes to {{ConfiguredFailoverProxyProvider}} and {{ObserverReadProxyProvider}}. This takes the approach of scanning through each proxy and checking the state; if it is not correct, try another one. Once a correct (observer) proxy is found, stay on that one until it fails. This is essentially a copy of how {{ConfiguredFailoverProxyProvider}} is implemented. I have a few outstanding TODOs about comments in the patch, but otherwise it should be ready for review. > Implement performFailover logic for ObserverReadProxyProvider. > -------------------------------------------------------------- > > Key: HDFS-13779 > URL: https://issues.apache.org/jira/browse/HDFS-13779 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: hdfs-client > Reporter: Konstantin Shvachko > Assignee: Erik Krogen > Priority: Major > Attachments: HDFS-13779-HDFS-12943.000.patch, > HDFS-13779-HDFS-12943.WIP00.patch > > > Currently {{ObserverReadProxyProvider}} inherits {{performFailover()}} method > from {{ConfiguredFailoverProxyProvider}}, which simply increments the index > and switches over to another NameNode. The logic for ORPP should be smart > enough to choose another observer, otherwise it can switch to a SBN, where > reads are disallowed, or to an ANN, which defeats the purpose of reads from > standby. > This was discussed in HDFS-12976. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org