hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [hadoop] vivekratnavel opened a new pull request #1311: HDDS-1946. CertificateClient should not persist keys/certs to ozone.m…
Date Sat, 17 Aug 2019 22:36:31 GMT
vivekratnavel opened a new pull request #1311: HDDS-1946. CertificateClient should not persist
keys/certs to ozone.m…
URL: https://github.com/apache/hadoop/pull/1311
 
 
   …etadata.dir
   
   The issue was that 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.
   
   The solution implemented in this patch is to store certs in a sub directory inside ozone.metadata.dir
based on the component. Ozone Manager will store its certs in `${ozone.metadata.dir}/om/certs`
and Datanode will  store in `${ozone.metadata.dir}/dn/certs` to avoid conflicts. This solution
was discussed with @anuengineer and I thank him for his guidance.
   
   Testing done: 
   I tested the patch in docker containers and verified that certs are now stored in `${ozone.metadata.dir}/${component}/certs`
path. I modified the unit tests and verified that all unit tests pass.
    

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

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


Mime
View raw message