You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:35:09 UTC

[jira] [Updated] (HDDS-3233) ReInitialize the proxy and DtService when rpcAddress is unresolved in RpcClient

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

Ethan Rose updated HDDS-3233:
-----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> ReInitialize the proxy and DtService when rpcAddress is unresolved in RpcClient
> -------------------------------------------------------------------------------
>
>                 Key: HDDS-3233
>                 URL: https://issues.apache.org/jira/browse/HDDS-3233
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>
> This Jira is to fix the issue of re-initialize the proxy object and dtservice(token service field) when fail Over happens. In this way, when failover happens, we retry again and compute the dtService.
> Right now, when the socket address is unresolved, we create a placeHolder address with an unresolvable socket. This Jira is to fix when later that OM address is resolvable, we try contacting that OM again from the client.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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