Edward J. Yoon pisze:
The pigi Looks fun. Thanks KG.
BTW, I saw the RESTful based blog builder, called 'bloog' on google
appengine. Does anyone try this on Hbase? :)
Hi
yes ... and no. We make some similar application - forum, but we use
pure java API instead of REST.
We estimate that
Good question.
Checkout bin/hbase-daemons.sh. You might be able to make this work for you
(try passing regionserver start as args).
Otherwise, we don't have a script to do this at moment. You need to run:
./bin/hbase regionserver stop
...across your cluster.
Doing above shuts things down cle
kill -0 region-server-pid should do the trick.
---
Jim Kellerman, Powerset (Live Search, Microsoft Corporation)
> -Original Message-
> From: Yair Even-Zohar [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 07, 2008 9:38 AM
> To: hbase-user@hadoop.apache.org
> Subject: RE: Question on A
Yair,
If all your nodes are authorized between each others (like having the same
ssh key and authorized_keys files on all nodes), you can simply do
"${HBASE_HOME}/bin/hbase-daemons.sh stop regionserver" on any of them, if
the conf/regionservers file is populated.
J-D
On Fri, Nov 7, 2008 at 12:37
How can we shut down the regieonservers cleanly if the master is down?
Thanks
-Yair
-Original Message-
From: Jim Kellerman (POWERSET) [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 8:54 AM
To: hbase-user@hadoop.apache.org
Subject: RE: Question on Availability
Jean-Daniel is c
Jean-Daniel is correct. Although HDFS has a "warm backup" for
the namenode, it requires physical intervention to start it
up if the primary namenode fails.
With respect to HBase, moving the master is not a big deal.
Shutting down the region servers (cleanly: no kill -9),
pushing a new config which
Thank you!
On Fri, Nov 7, 2008 at 4:52 PM, Jean-Daniel Cryans <[EMAIL PROTECTED]> wrote:
> Michael,
>
> The Namenode is also a SPOF.
>
> On keeping a separate cluster for failover, until we add higher
> availability, it depends on how much uptime you need to provide I guess. I
> personally never s
Thanks !
On Fri, Nov 7, 2008 at 5:20 PM, Cosmin Lehene <[EMAIL PROTECTED]> wrote:
> Updating all region servers configuration to reflect the new master address
> and restarting the cluster will do it. It's a matter of minutes. We tested
> this and I can confirm it works.
>
> Cosmin
>
Updating all region servers configuration to reflect the new master address and
restarting the cluster will do it. It's a matter of minutes. We tested this and
I can confirm it works.
Cosmin
On 11/7/08 4:52 PM, "Jean-Daniel Cryans" <[EMAIL PROTECTED]> wrote:
Michael,
The Namenode is also a S
Michael,
The Namenode is also a SPOF.
On keeping a separate cluster for failover, until we add higher
availability, it depends on how much uptime you need to provide I guess. I
personally never saw a machine hosting a Master failing, so I'm not sure on
how clean it can be regards the META, but I
Jarod,
Some informations are missing. Is it only 1 table you have? How did you try
to count the number of rows the first time? If you are using only 1 client,
scanning is sequential so it's normal to have only 1 region server taking
all the hits at a time. Maybe try using the RowCounter mapreduce
Hi, all
I guess that Hbase master server is a single point of failure. Is
it correct ? Does Hbase (I mean the whole stack -- HDFS + Hbase) have
any other single point of failure ?
If Hbase has a single point of failure we should arrange a backup
Hbase cluster to switch to it in case of fa
Hi ,
I'm using hbase0.2.1 + hadoop 0.17 with 11 client & 1master servers
I crawl some data and save them to hbase with map & reduce.
after that , I try to count the total number of some data.
it too slow , you can see the monitor , 1 of clients have a high request ,
but others is 0.
S1:60020 1226
13 matches
Mail list logo
