Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo, mail # user - Can't get Accumulo 1.5 monitor interface to start in my browser

Copy link to this message
Re: Can't get Accumulo 1.5 monitor interface to start in my browser
Pete Carlson 2013-09-11, 18:08
How do I determine if the rest of Accumulo is up and running since I can't
use the monitor?

Inside the monitor logs I see messages that it connected to Hadoop and
Zookeeper, but then later on I see this message stating there are no tablet

2013-09-11 11:39:29,199 [server.Accumulo] WARN :  System swappiness setting
is greater than ten (60) which can cause time-sensitive operations to be
delayed.  Accumulo is time sensitive because it needs to maintain
distributed lock agreement.
2013-09-11 11:39:32,506 [impl.ServerClient] WARN :
tracer:localhost.localdomain There are no tablet servers: check that
zookeeper and accumulo are running.

And when I log in to the accumulo shell I get the warning: There are no
tablet servers: check that zookeeper and accumulo are running.

Could the system swappiness setting of 60 be causing my issue?


On Wed, Sep 11, 2013 at 1:13 PM, John Vines <[EMAIL PROTECTED]> wrote:

> Is the rest of Accumulo up and running? And is that the only type of error
> in the Monitor logs?
> On Wed, Sep 11, 2013 at 1:04 PM, Pete Carlson <[EMAIL PROTECTED]> wrote:
>> Ok, I deleted /accumulo out of hdfs, initialized accumulo, and re-started
>> Accumulo.  I still can't see the monitor IN my VM browser.  I still get the
>> same Monitor info message in the logs.
>> Pete
>> On Wed, Sep 11, 2013 at 11:55 AM, John Vines <[EMAIL PROTECTED]> wrote:
>>> You need to delete the /accumulo directory out of hdfs
>>> On Wed, Sep 11, 2013 at 11:54 AM, Pete Carlson <[EMAIL PROTECTED]>wrote:
>>>> I removed the monitor certificates as suggested, and I no longer get
>>>> any messages in the monitor_localhost.err file.
>>>> When I look in the monitor_localhost.localdomain.log file and saw the
>>>> following INFO/Exception message:
>>>> 2013-09-11 11:42:50,012 [monitor.Monitor] INFO :  Failed to obtain
>>>> problem reports
>>>> java.lang.RuntimeException:
>>>> org.apache.accumulo.core.client.impl.ThriftScanner$ScanTimedOutException
>>>>         at
>>>> org.apache.accumulo.core.client.impl.ScannerIterator.hasNext(ScannerIterator.java:174)
>>>>         at
>>>> org.apache.accumulo.server.problems.ProblemReports$3.hasNext(ProblemReports.java:241)
>>>>         at
>>>> org.apache.accumulo.server.problems.ProblemReports.summarize(ProblemReports.java:299)
>>>>         at
>>>> org.apache.accumulo.server.monitor.Monitor.fetchData(Monitor.java:392)
>>>>         at
>>>> org.apache.accumulo.server.monitor.Monitor$2.run(Monitor.java:504)
>>>>         at
>>>> org.apache.accumulo.core.util.LoggingRunnable.run(LoggingRunnable.java:34)
>>>>         at java.lang.Thread.run(Thread.java:724)
>>>> Caused by:
>>>> org.apache.accumulo.core.client.impl.ThriftScanner$ScanTimedOutException
>>>>         at
>>>> org.apache.accumulo.core.client.impl.ThriftScanner.scan(ThriftScanner.java:212)
>>>>         at
>>>> org.apache.accumulo.core.client.impl.ScannerIterator$Reader.run(ScannerIterator.java:82)
>>>>         at
>>>> org.apache.accumulo.core.client.impl.ScannerIterator.hasNext(ScannerIterator.java:164)
>>>>         ... 6 more
>>>> I was thinking this was related to the fact I didn't yet have Thrift
>>>> 0.9.0 installed (due to dependency issues).  I now have Thrift 0.9.0
>>>> installed.  I saved off my config files, blew away the accumulo directory
>>>> and extracted it again from the tar.gz and copied over my conf files.
>>>> However, when I run the accumulo-1.5.0/bin/accumulo init command again
>>>> it gives me the following error:
>>>> [util.Initialize] FATAL: It appears this location was previously
>>>> initialized, exiting ...
>>>> I can still start Accumulo like before with the bin/start-all.sh
>>>> command but the Accumulo monitor still doesn't work IN my VM.
>>>> Any other ideas to try?
>>>> Pete
>>>> On Wed, Sep 11, 2013 at 10:57 AM, John Vines <[EMAIL PROTECTED]> wrote:
>>>>> Either try rerunning the monitor certificates or remove the portion
>>>>> from your accumulo-site that defines use of the certificate. I suggest the