All

we have hbase on our laptops at work, when we switch to go home with the same laptop and get a new IP address hbase won't startup. Is there a solution for this?

What error do you run into specifically? Do you run bound to localhost
or external address? If latter, do you have a hostname also being
dynamically updated to resolve to the same?

Try wiping your ZK clean, before starting HBase. Depending on your ZK
version, try over zkCli.sh: "rmr /hbase" or "deleteall /hbase", or you
may have to individually delete each node under /hbase with "rm
/hbase/<node>" (autocomplete works under zkCli.sh shell).

On Sat, Jan 21, 2012 at 7:24 PM, Ben Cuthbert <[EMAIL PROTECTED]> wrote:
> All
>
> we have hbase on our laptops at work, when we switch to go home with the same laptop and get a new IP address hbase won't startup. Is there a solution for this?
>
>

--
Harsh J
Customer Ops. Engineer, Cloudera

IIRC when it starts it will start looking for the cached IPs which timeout
and it's going to retry 3 times with 60 seconds or so for each region.
Eventually if you start it again it should start.

On 1/21/12 7:44 AM, "Harsh J" <[EMAIL PROTECTED]> wrote:

>What error do you run into specifically? Do you run bound to localhost
>or external address? If latter, do you have a hostname also being
>dynamically updated to resolve to the same?
>
>Try wiping your ZK clean, before starting HBase. Depending on your ZK
>version, try over zkCli.sh: "rmr /hbase" or "deleteall /hbase", or you
>may have to individually delete each node under /hbase with "rm
>/hbase/<node>" (autocomplete works under zkCli.sh shell).
>
>On Sat, Jan 21, 2012 at 7:24 PM, Ben Cuthbert <[EMAIL PROTECTED]>
>wrote:
>> All
>>
>> we have hbase on our laptops at work, when we switch to go home with
>>the same laptop and get a new IP address hbase won't startup. Is there a
>>solution for this?
>>
>>
>
>
>
>--
>Harsh J
>Customer Ops. Engineer, Cloudera