You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Xiaoyu Yao (Jira)" <ji...@apache.org> on 2020/04/09 05:37:00 UTC
[jira] [Updated] (HDDS-3365) Ensure OzoneConfiguration is
initialized in OzoneClientFactory#getOzoneClient
[ https://issues.apache.org/jira/browse/HDDS-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoyu Yao updated HDDS-3365:
-----------------------------
Summary: Ensure OzoneConfiguration is initialized in OzoneClientFactory#getOzoneClient (was: Ensure OzoneConfiguration is initialized OzoneClientFactory#getOzoneClient)
> Ensure OzoneConfiguration is initialized in OzoneClientFactory#getOzoneClient
> -----------------------------------------------------------------------------
>
> Key: HDDS-3365
> URL: https://issues.apache.org/jira/browse/HDDS-3365
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Affects Versions: 0.5.0
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Priority: Major
>
> HDDS-3319 added a new method to get RPCClient based on the omserviceID in OzoneToken. However, some om.service.id compare logic is based on a Hadoop Configuration object. As a result, the om configuration may not be loaded if the Configuration is a Hadoop Configuration only (e.g., RM).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org