hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hanisha Koneru (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-1072) Implement RetryProxy and FailoverProxy for OM client
Date Thu, 28 Feb 2019 19:41:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Hanisha Koneru updated HDDS-1072:
    Attachment: HDDS-1072.004.patch

> 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: OM
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>            Priority: Major
>         Attachments: HDDS-1072.001.patch, HDDS-1072.002.patch, HDDS-1072.003.patch, HDDS-1072.004.patch
> 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
> # 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message