[
https://issues.apache.org/jira/browse/HDDS-1072?focusedWorklogId=207085&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-207085
]
ASF GitHub Bot logged work on HDDS-1072:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Mar/19 11:20
Start Date: 04/Mar/19 11:20
Worklog Time Spent: 10m
Work Description: elek commented on pull request #548: Revert "HDDS-1072.
Implement RetryProxy and FailoverProxy for OM clie…
URL: https://github.com/apache/hadoop/pull/548
Trunk seems to be broken by HDDS-1072.
Let's check this revert commit with jenkins, to be sure this is the problem.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 207085)
Time Spent: 10m
Remaining Estimate: 0h
> Implement RetryProxy and FailoverProxy for OM client
> ----------------------------------------------------
>
> Key: HDDS-1072
> URL: https://issues.apache.org/jira/browse/HDDS-1072
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Manager
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
> Labels: pull-request-available
> Attachments: HDDS-1072.001.patch, HDDS-1072.002.patch,
> HDDS-1072.003.patch, HDDS-1072.004.patch, HDDS-1072.005.patch,
> HDDS-1072.006.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> RPC Client should implement a retry and failover proxy provider to failover
> between OM Ratis clients. The failover should occur in two scenarios:
> # When the client is unable to connect to the OM (either because of network
> issues or because the OM is down). The client retry proxy provider should
> failover to next OM in the cluster.
> # When OM Ratis Client receives a response from the Ratis server for its
> request, it also gets the LeaderId of server which processed this request
> (the current Leader OM nodeId). This information should be propagated back to
> the client. The Client failover Proxy provider should failover to the leader
> OM node. This helps avoid an extra hop from Follower OM Ratis Client to
> Leader OM Ratis server for every request.
--
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
