You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2009/04/01 07:59:13 UTC

[jira] Commented: (ZOOKEEPER-357) ZooKeeper cannot actually take care of a Zoo

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694401#action_12694401 ] 

Mahadev konar commented on ZOOKEEPER-357:
-----------------------------------------

ben,
is this is an april fool's joke? 

> ZooKeeper cannot actually take care of a Zoo
> --------------------------------------------
>
>                 Key: ZOOKEEPER-357
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-357
>             Project: Zookeeper
>          Issue Type: Bug
>            Reporter: Benjamin Reed
>            Priority: Critical
>
> Last week I setup an unattended ZooKeeper cluster that I expected to be able to take care of things while I was on vacation. I used 7 dedicated servers with two disks. I had done extensive burn in testing of the servers, so I fully expected the system to work problem free for the entire week. Indeed, when I returned yesterday none of the 7 servers had any hardware or software problem the entire time nor had there been any network problems. On the other hand the Zoo was in complete chaos. Even though there were no errors in the ZooKeeper log most of the animals were near starvation, except for the lions who had gotten loose and eaten some of the pigs. I'll not even go into the stench from the dirty cages!
> Either the documentation needs to more clearly explain how to configure the server properly in the Zoo environment, or it should clearly state that ZooKeeper cannot take care of the Zoo out of the box!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.