[
https://issues.apache.org/jira/browse/AMBARI-22549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271420#comment-16271420
]
Robert Levas commented on AMBARI-22549:
---------------------------------------
I was thinking that upon install/setup (via {{ambari-server setup}}), a record
would be added to the {{hosts}} table. Since we don't want to cause any
conflicts if an agent is registered for the Ambari server host, a bogus
hostname would be set in the table. I believe that hostname (host_name column)
is the only unique field in that table. Maybe the hostname could be someting
like "ambari.server.local". Then we can easily find it in a query for the host
ID.
[~echekanskiy] brought up concerns of possible heartbeat errors and other
artifacts due to this host record. However, I thought that since it wont be in
the {{clusterhostmapping}} table, the host will effectively be _hidden_. We
will need to test this out and if necessary add a flag to the host table to
indicate that it should be ignored by most operations.
> 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)
