[Hadoop Wiki] Update of "ZooKeeper/HBaseUseCases" by stack

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "ZooKeeper/HBaseUseCases" page has been changed by stack.
http://wiki.apache.org/hadoop/ZooKeeper/HBaseUseCases?action=diff&rev1=2&rev2=3

--------------------------------------------------

  == Current Usecases ==
  Current use cases
  
- === Case 1 (please fill these in) ===
- Summary: (summary of a particular use of zk)
+ == Near Future Usecases 0.21 HBase ==
+ === Case 1 ===
+ Summary: HBase Table State and Schema Changes
+ Expected scale: Thousands of RegionServers watching ready to react to changes with about 100 tables each of which can have 1 or 2 states and an involved schema
  
- Expected scale: (how many clients, nodes, watches, req/s, etc...)
+ General recipe implemented: A better description of problem and sketch of the solution can be found at [[http://wiki.apache.org/hadoop/Hbase/MasterRewrite#tablestate|Master Rewrite: Table State]]
  
- General recipe implemented: (some basic psudocode would be useful)
+ === Case 2 ===
+ Summary: HBase Region Transitions from unassigned to open and from open to unassigned with some intermediate states
+ Expected scale: 100k regions across thousands of RegionServers
  
+ General recipe implemented: None yet.  Need help.  Was thinking of keeping queues up in zk -- queues per regionserver for it to open/close etc.  But the list of all regions is kept elsewhere currently and probably for the foreseeable future out in our .META. catalog table.  Some further description can be found here [[http://wiki.apache.org/hadoop/Hbase/MasterRewrite#regionstate|Master Rewrite: Region State]]
+ 
- == Future Interest ==
+ == Far Future Interest ==
  Potential uses going forward