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-12, 00:39
Josh,

I think this would be good info to include in the user guide, perhaps as
steps to configure the monitor (ie around the section where it talks about
the monitor url).  Another useful area for the info would be under
configuration (where the user guide talks about setting the monitor,
master, slave settings, etc under the  accumulo /conf directory.

Thanks,

Pete
On Sep 11, 2013 7:52 PM, "Josh Elser" <[EMAIL PROTECTED]> wrote:

> Pete,
>
> I assume you did some leg-work before hitting up the mailing list...  any
> recommendations on where you think might make sense on encapsulating some
> of this information?
>
> FAQ format? Rolled into documentation (user/admin guide)? Other?
>
> - josh
>
> On 09/11/2013 04:17 PM, Pete Carlson wrote:
>
>> All,
>>
>> I resolved the issue.  Per Eric's suggestion I changed my swappiness
>> setting down to 10, and also disabled all IPV6 stuff on my VM.  Once I did
>> this and changed the IP address of my monitor to 127.0.0.1 my monitor
>> started working.
>>
>> Thanks guys. :-)
>>
>> Regards,
>>
>> Pete
>>
>> On Wed, Sep 11, 2013 at 2:12 PM, John Vines <[EMAIL PROTECTED] <mailto:
>> [EMAIL PROTECTED]>> wrote:
>>
>>     Furthermore, tservers being down shouldn't prevent the monitor
>>     page from coming up at all, so check for any other relevant
>>     messages in of the monitor's logs.
>>
>>
>>     On Wed, Sep 11, 2013 at 2:08 PM, Pete Carlson <[EMAIL PROTECTED]
>>     <mailto:[EMAIL PROTECTED]>> wrote:
>>
>>         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 servers:
>>
>>         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?
>>
>>         Regards,
>>
>>         Pete
>>
>>
>>         On Wed, Sep 11, 2013 at 1:13 PM, John Vines <[EMAIL PROTECTED]
>>         <mailto:[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] <mailto:[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] <mailto:[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] <mailto:[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: