[ https://issues.apache.org/jira/browse/ACCUMULO-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559147#comment-14559147 ]
Josh Elser commented on ACCUMULO-3837: -------------------------------------- Before you go changing things, why is the approach I outlined in the description not viable? > "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)