accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2481) Monitor should still work if HDFS + Zookeeper go away
Date Fri, 14 Mar 2014 21:46:43 GMT

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

Sean Busbey commented on ACCUMULO-2481:
---------------------------------------

For completeness, I left pages loading with a shut down hdfs + zk for 10 minutes. After I
restarted hdfs and zk services, the monitor pages all loaded.

logs showed message from most services claiming zk problems and intent to retry. Everyone
recovered and appeared to function normally again after.

> Monitor should still work if HDFS + Zookeeper go away
> -----------------------------------------------------
>
>                 Key: ACCUMULO-2481
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2481
>             Project: Accumulo
>          Issue Type: Bug
>          Components: monitor
>    Affects Versions: 1.4.4, 1.4.5
>         Environment: 1.4.5-SNAPSHOT on CDH4.5.0.
> Non-HA cluster with 2 workers and a single Zookeeper server.
>            Reporter: Sean Busbey
>            Priority: Minor
>             Fix For: 1.4.6
>
>
> While preparing to update a test cluster, I accidentally attempted to refresh some monitor
pages after I had shut down the underlying HDFS and Zookeeper services. The page simply hung.
I've since tried loading several different pages (overview, logs, master view) and all simple
hang on the monitor's end. If I restart the underlying cluster, the pages resolve like normal.
> I haven't had a chance to see if this happens on later versions, nor figure out which
missing component matters.
> Expected behavior would be for the monitor to still load, albeit with a bunch of alarm
bells about everything being off.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message