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 Tue, 02 Dec 2014 17:42:12 GMT

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

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

The start-here.sh script works hard to figure out the role of the server, hunting for its
name in the various files.  When it finds itself, it starts the appropriate process.  However,
it tells it to bind to the fqdn that it looked up, and not the name listed in the file.

This is a minor issue, but I like to keep the operations people happy.


> 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