[
https://issues.apache.org/jira/browse/AMBARI-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765977#comment-13765977
]
Dilli Arumugam commented on AMBARI-3215:
----------------------------------------
Please note configuration property changes required in ambari-server when it
has to talk to SSL enabled haddop HTTP Web end points:
/etc/ambari-server/conf/ambari.properties
should define values for keys ssl.trustStore.path, ssl.trustStore.password,
ssl.trustStore.type
I tested with the following values for the keys
ssl.trustStore.path=/etc/ambari-server/conf/truststore.jks
ssl.trustStore.password=truststorepass
ssl.trustStore.type=jks
You should have imported the certificates of your Hadoop Web Endpoints into the
truststore.
> ambari server should use https instead of http to talk to ssl enabled hadoop
> ----------------------------------------------------------------------------
>
> Key: AMBARI-3215
> URL: https://issues.apache.org/jira/browse/AMBARI-3215
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Reporter: Dilli Arumugam
> Assignee: Dilli Arumugam
> Attachments: AMBARI-3215.patch
>
>
> Ambari server attempts to talk http to Hadoop HTTP end points even when
> Hadoop HTTP end points are SSL enabled. This causes connection failure and
> ambari server is not able to get JMX data.
> Ambari server should check core-site.xml hadoop.ssl.enabled property and
> switch to HTTPS protocol appropriately.
> How to verify the fix:
> Without the fix, ambari-server log would report ERROR like the following:
> 21:58:00,988 ERROR pool-1-thread-34 JMXPropertyProvider:446 - Caught
> exception getting JMX metrics : Connection refused
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
