accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3378) server reports different hostname with "start-here.sh"
Date Thu, 04 Dec 2014 19:05:12 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234486#comment-14234486
] 

Eric Newton commented on ACCUMULO-3378:
---------------------------------------

Actually, the start-server script is doing this:

{noformat}
# When the hostname provided is the alias/shortname, try to use the FQDN to make
# sure we send the right address to the Accumulo process.
if [[ "$HOST" = "$(hostname -s)" ]]; then
    HOST="$(hostname -f)"
    ADDRESS="$HOST"
fi
{noformat}

This works fine when start-server is run locally (which is always the case with start-here).
 But it does not work when it ssh's to start the server.

> server reports different hostname with "start-here.sh"
> ------------------------------------------------------
>
>                 Key: ACCUMULO-3378
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3378
>             Project: Accumulo
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 1.6.0, 1.6.1
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Minor
>             Fix For: 1.6.2, 1.7.0
>
>
> Local operations people have been re-starting tservers with "start-here.sh" which restarts
the servers with the fqdn. This creates confusion between the same server when started with
the simple hostname.  The monitor reports the simply named server as down, but the server
is now up with the fqdn reporting as its address.
> Work around: put the fqdn in the slaves file.  Sadly this makes everything display the
ugly long fqdn everywhere.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message