Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 18 Dec 2014 03:51:15 +0000 (UTC)
From: "Corey J. Nolet (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12758915.1417532936000.53485.1418874675126@Atlassian.JIRA>
In-Reply-To: <JIRA.12758915.1417532936000@Atlassian.JIRA>
References: <JIRA.12758915.1417532936000@Atlassian.JIRA>
 <JIRA.12758915.1417532936338@arcas>
Subject: [jira] [Updated] (ACCUMULO-3378) server reports different hostname
 with "start-here.sh"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey J. Nolet updated ACCUMULO-3378:
-------------------------------------
    Fix Version/s:     (was: 1.6.2)
                   1.6.3

> 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.7.0, 1.6.3
>
>
> 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)