[
https://issues.apache.org/jira/browse/AMBARI-22549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271582#comment-16271582
]
Jonathan Hurley commented on AMBARI-22549:
------------------------------------------
I don't see why an entry in the hosts table would cause problems if that host
is not mapped. I dislike a name-based identification model, like
"ambari.server.local" ... especially when in the event that Ambari is installed
in the cluster, we would essentially have a duplicate.
Could we make it a column which identifies a host as the ambari server? Having
a real FQDN might provide useful at some point and it would prevent duplication
in the event Ambari is part of the cluster.
> Add the Ambari server host to hosts table in an identifiable way
> ----------------------------------------------------------------
>
> Key: AMBARI-22549
> URL: https://issues.apache.org/jira/browse/AMBARI-22549
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 3.0.0
> Reporter: Robert Levas
> Assignee: Eugene Chekanskiy
> Fix For: 3.0.0
>
>
> Add the Ambari server host to hosts table in an identifiable way so that
> information tied to a host can be tied to the Ambari server host in the event
> an agent is not registered for that host.
> This host record should not be seen via in UI or cause heartbeat issues. It
> should remain _hidden_ except for internal usages. For example,
> host_role_command and keytab file details.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
