hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "HBase Review Board (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1511) Pseudo distributed mode in LocalHBaseCluster
Date Fri, 08 Oct 2010 22:16:35 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919396#action_12919396

HBase Review Board commented on HBASE-1511:

Message from: stack@duboce.net

bq.  On 2010-07-16 13:39:10, stack wrote:
bq.  > trunk/bin/local-master-backup.sh, line 1
bq.  > <http://review.cloudera.org/r/328/diff/1/?file=2844#file2844line1>
bq.  >
bq.  >     Why is it called local-master-backup?  Should be a more descriptive name?  Its
the 'backup' that throws me off.  'local-masters'?
bq.  >
bq.  Nicolas wrote:
bq.      This JIRA also needs an associated wiki article change.  So, the workflow would be:
bq.      ./bin/start-hbase.sh
bq.      ./bin/local-master-backup start 1
bq.      I don't think you would want to use this file to start the original master, use start-hbase.sh
for that.  You primarily want to use this script to test master failover conditions.

Don't write a wiki article.  Add an article under src/site, under xdoc or apt (not yet in
place).  This can be done in a separate issue.  Meantime, on commit I can add the above  on
how its used (w/o it, I was a little baffled but just those few lines above explain it all
-- for me at least).

bq.  On 2010-07-16 13:39:10, stack wrote:
bq.  > trunk/bin/local-master-backup.sh, line 10
bq.  > <http://review.cloudera.org/r/328/diff/1/?file=2844#file2844line10>
bq.  >
bq.  >     Explain 'offset' in this usage output?  (Seems to be port offset from default?)
bq.  Nicolas wrote:
bq.      offset is not only the port offset, but also an identifier for the logs.  The log
for "./bin/local-master-backup.sh start 1" would be located at logs/hbase-<user>-1-master-<server>.log
bq.      In an internal review, Kannan asked why you couldn't use "start 0", I thought offset
would help explain that issue.  opinions?

Hmm... maybe you do need an article on how this stuff works.   Smile.  Offset is fine (Is
Kannan saying that a 'start 0' should be rejected?).  If you put together a paragraph or two,
I'll take care of sticking it into proper format.

- stack

This is an automatically generated e-mail. To reply, visit:

> Pseudo distributed mode in LocalHBaseCluster
> --------------------------------------------
>                 Key: HBASE-1511
>                 URL: https://issues.apache.org/jira/browse/HBASE-1511
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.19.3
>            Reporter: Evgeny Ryabitskiy
>            Assignee: Nicolas Spiegelberg
>            Priority: Minor
>             Fix For: 0.90.0
>         Attachments: HBASE-1511.patch, psuedo-distribute hbase usage.txt
> After changes to config and adding of parameter:
> {code}
>   <property>
>     <name>hbase.cluster.distributed</name>
>     <value>false</value>
>     <description>The mode the cluster will be in. Possible values are
>       false: standalone and pseudo-distributed setups with managed Zookeeper
>       true: fully-distributed with unmanaged Zookeeper Quorum (see hbase-env.sh)
>     </description>
>   </property>
> {code}
> running HBase in pseudo destr mode become not so easy, I think description for false
variant is wrong and you can't get pseudo-distributed mode setting this option to false now.
> I wish to have some option in LocalHBaseCluster for pseudo destr mode where I wish to
>  * separate processes for Master and HRSs
>  * ability to dynamically change HRS number in cluster
>  * managed ZK cluster (like it is in local mode now)
>  * managed small local HDFS cluster
> I think it is very useful for testing, debugging and for user experience with HBase,
who want to try something close to real HBase not some emulation in standalone mode.

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

View raw message