You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Akhil S Naik (JIRA)" <ji...@apache.org> on 2019/02/06 06:09:00 UTC
[jira] [Commented] (AMBARI-24961) Ambari is unable to parse
{{hostname}} in {hdfs-site/dfs.datanode.address} and is triggering alert
for datanode process
[ https://issues.apache.org/jira/browse/AMBARI-24961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761516#comment-16761516 ]
Akhil S Naik commented on AMBARI-24961:
---------------------------------------
[~rlevas] ,
Could you please help me review this BUG.
i guess we should consider case of {{hostname}} while looking for localhost.
> Ambari is unable to parse {{hostname}} in {hdfs-site/dfs.datanode.address} and is triggering alert for datanode process
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-24961
> URL: https://issues.apache.org/jira/browse/AMBARI-24961
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: trunk, 2.6.2, 2.7.0
> Environment: ambari-2.6.2
> ambari-2.7.0
> trunk
> Reporter: Akhil S Naik
> Assignee: Akhil S Naik
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Ambari is unable to parse \\{\{hostname\}\} in {hdfs-site/dfs.datanode.address} and is triggering alert for datanode process
> I changed the value of dfs.datanode.address in Advanced hdfs configuration using ambari
> i set value to \\{\{hostname\}\}:50010 ( default value is 0.0.0.0:50010 )
> Now after restart datanode is working fine and but ambari is triggering alert on datanode process with error :
> "Connection failed: [Errno -2] Name or service not known to \\{\{hostname\}\}:50010"
> expected result : Ambari shouldnt trigger the alert and it should pass \\{\{hostname\}\} correctly to localhost
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)