[
https://issues.apache.org/jira/browse/HDDS-1946?focusedWorklogId=302453&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-302453
]
ASF GitHub Bot logged work on HDDS-1946:
----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Aug/19 23:00
Start Date: 27/Aug/19 23:00
Worklog Time Spent: 10m
Work Description: xiaoyuyao commented on pull request #1311: HDDS-1946.
CertificateClient should not persist keys/certs to ozone.m…
URL: https://github.com/apache/hadoop/pull/1311#discussion_r318331343
##########
File path:
hadoop-hdds/client/src/main/java/org/apache/hadoop/hdds/scm/XceiverClientGrpc.java
##########
@@ -70,6 +70,7 @@
*/
public class XceiverClientGrpc extends XceiverClientSpi {
static final Logger LOG = LoggerFactory.getLogger(XceiverClientGrpc.class);
+ private static final String COMPONENT = "dn";
Review comment:
This may not work as expected. XCeiverClientGrpc is also use by ozone client
to read key/file, using "dn" means we allows MR task running on datanode to use
DN's key/cert for TLS? For client outside ozone cluster, they will not be able
to connect TLS enabled GRPC endpoint.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 302453)
Time Spent: 3h (was: 2h 50m)
> CertificateClient should not persist keys/certs to ozone.metadata.dir
> ---------------------------------------------------------------------
>
> Key: HDDS-1946
> URL: https://issues.apache.org/jira/browse/HDDS-1946
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Xiaoyu Yao
> Assignee: Vivek Ratnavel Subramanian
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h
> Remaining Estimate: 0h
>
> For example, when OM and SCM are deployed on the same host with
> ozone.metadata.dir defined. SCM can start successfully but OM can not because
> the key/cert from OM will collide with SCM.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
