[
https://issues.apache.org/jira/browse/AMBARI-12915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741060#comment-14741060
]
Jeffrey E Rodriguez commented on AMBARI-12915:
-----------------------------------------------
Hi Greg. For the record, can you are more details?
What JVM were you using when you were trying suggestion?
Not all version of JVM have fixed this issue. and the JDK workaround adding
only apply to sun/openjdk releases that added this.
You can still check DH length using openssl are suggested.
> Make agent hostname configurable
> --------------------------------
>
> Key: AMBARI-12915
> URL: https://issues.apache.org/jira/browse/AMBARI-12915
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent
> Affects Versions: 2.1.0
> Reporter: Greg Hill
> Assignee: Greg Hill
> Priority: Minor
> Attachments: AMBARI-12915.patch
>
>
> Currently the agent can either get the hostname from the local system, or you
> can inject a script to tell it what hostname to use using the
> 'hostname_script' config value. I would like to add a 'hostname' config
> value to the agent section of the agent config so we can just tell the agent
> what hostname to use.
> The scenario this comes up in is that our Ambari setup uses a local DNS
> domain for internal traffic, but the Ambari API has a public FQDN that we use
> for the API. It would be much cleaner for us to just specify the hostname in
> the config rather than jumping through hoops to generate a script to use to
> derive it.
> https://github.com/apache/ambari/blob/087d9003ecf6af33890e4f48743d7237a30d6438/ambari-agent/src/main/python/ambari_agent/hostname.py#L40
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
