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-3837) "Instance Name: null" appears when Monitor first starts
Date Tue, 26 May 2015 14:13:18 GMT

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

Eric Newton commented on ACCUMULO-3837:
---------------------------------------

That's not a bug, it's a feature. From the code:
bq. // Learn our instance name asynchronously so we don't hang up if zookeeper is down

I'll decrease the timeout from 1s to 0s, and make the default value more explanatory.


> "Instance Name: null" appears when Monitor first starts
> -------------------------------------------------------
>
>                 Key: ACCUMULO-3837
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3837
>             Project: Accumulo
>          Issue Type: Bug
>          Components: monitor
>            Reporter: Josh Elser
>             Fix For: 1.6.3, 1.8.0, 1.7.1
>
>
> This is one of those infuriating "it's always been like this" bugs with the monitor.
> The monitor lazily initializes itself with information from the Master. One of these
is the Instance Name for the cluster. So, when you first visit the monitor, you'll notice
that you get "Instance Name: null" in the header.
> Eventually the actual instance name will get filled in. We can do better than propagate
"null" to our users. The monitor knows the directory in HDFS and thus the instance ID. It
can also get the instance name from the mapping in HDFS. Best as I understand, it's just lazy
that we don't do this.



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

Mime
View raw message