You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/04/22 18:46:48 UTC
[jira] Updated: (HBASE-1329) Visibility into ZooKeeper
[ https://issues.apache.org/jira/browse/HBASE-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1329:
-------------------------
Priority: Blocker (was: Major)
Marking this issue a blocker. We need to do all we can to avoid hbase users having the impression that zookeeper is a black box.
@Patrick -> Thanks for the great suggestions -- IMO, the last one sounds most promising.
> Visibility into ZooKeeper
> -------------------------
>
> Key: HBASE-1329
> URL: https://issues.apache.org/jira/browse/HBASE-1329
> Project: Hadoop HBase
> Issue Type: New Feature
> Affects Versions: 0.20.0
> Reporter: Nitay Joffe
> Priority: Blocker
>
> Currently, to the users of HBase ZooKeeper is some mysterious thing that is for some reason important but no one knows why. We need to provide more visibility into ZooKeeper from HBase.
> This issue is to start a discussion on what sorts of things we can/should provide. Some possible ideas to get started:
> - Running a REST server. See ZOOKEEPER-36.
> - FUSE support. See ZOOKEEPER-25.
> - Admin/surgery tools in HBase shell. Answer questions like "in safe mode?"
> - Status and information on HBase's data in ZooKeeper in the web UI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.