accumulo-notifications mailing list archives

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

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

Josh Elser commented on ACCUMULO-3378:
--------------------------------------

bq.  I'm not going to spend any more time on this.

Is that a "I don't think it's worth it to fix it" or a "I don't care to spend any time myself"?

IMO, using FQDNs makes the most sense, but, if we do expect that, we should update the user
manual to recommend that (if it doesn't already).

> 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
>            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