[
https://issues.apache.org/jira/browse/ACCUMULO-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559162#comment-14559162
]
Josh Elser commented on ACCUMULO-3837:
--------------------------------------
bq. You can get the instance ID, but not the instance Name from HDFS.
Ugh, right. Sorry. Getting the wires crossed
Some other thoughts:
* Why not centralize this in the monitor that we can wait to get the instance
name once before the HTTP server comes up instead of in each servlet? Can still
do a timeout there if we don't get an answer in ~5 seconds, w/ a timer thread
to refresh.
* Something other than "null" would also be preferable for the "we couldn't
figure out the instance name" case since displaying "null" implies a bug in the
system (not a feature _smirk_)
Thank you for looking at this. I meant to get to it myself, but haven't yet.
> "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
> Assignee: Eric Newton
> 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)
