On Thu, Sep 22, 2011 at 4:41 AM, Stack <[email protected]> wrote:
> The bit about 1ms ping times sounds a bit good to me but Dan below
> says is better.
> St.Ack

I am not using EC2 but it is a good analogy :)

pa-hbase-master-na-7001.iad7$ ping pa-hbase-datanode-na-1024.vdc
PING pa-hbase-datanode-na-1024.vdc (10.119.133.76) 56(84) bytes of data.
64 bytes from pa-hbase-datanode-na-1024.vdc (10.119.133.76):
icmp_seq=1 ttl=58 time=0.812 ms
64 bytes from pa-hbase-datanode-na-1024.vdc (10.119.133.76):
icmp_seq=2 ttl=58 time=0.789 ms
64 bytes from pa-hbase-datanode-na-1024.vdc (10.119.133.76):
icmp_seq=3 ttl=58 time=0.787 ms

pa-hbase-master-na-7001.iad7$ ping pa-hbase-datanode-na-6004.iad6
PING pa-hbase-datanode-na-6004.iad6 (10.194.179.68) 56(84) bytes of data.
64 bytes from pa-hbase-datanode-na-6004.iad6 (10.194.179.68):
icmp_seq=1 ttl=58 time=1.54 ms
64 bytes from pa-hbase-datanode-na-6004.iad6 (10.194.179.68):
icmp_seq=2 ttl=58 time=1.54 ms
64 bytes from pa-hbase-datanode-na-6004.iad6 (10.194.179.68):
icmp_seq=3 ttl=58 time=1.58 ms


What about the RS shutdown problem? I don't see the connection between
the ping time and the fact that same threads will not close.

Regards,
Bogdan

>
> On Wed, Sep 21, 2011 at 6:21 PM, Daniel Washburn
> <[email protected]> wrote:
>>
>> On Sep 21, 2011, at 1:51 PM, Bogdan Ghidireac wrote:
>>
>>>> HBase and HDFS are not made to span datacenters.
>>>
>>> Yes, I know. I think the correct terminology is 3 availability zones
>>> within the same region (ping between them is about 1ms)
>>
>> [snip]
>>
>>>>
>>>> Is my assumption correct? Should I open a JIRA?
>>>>
>>>
>>> You could paste the thread dump but before doing anything, I'd suggest
>>> you change your layout so cluster runs inside a single datacenter.
>>>
>>> St.Ack
>>
>> Echoing St.ack's advice, but not wanting to sound like I'm scolding, you 
>> really should consider moving your AMIs into a single Availability Zone.  
>> EC2 puts up some impressive availability numbers as a platform, but when you 
>> stack several layers of software onto it, you start to push the limits of 
>> the availability zone SLA, and certainly the availability requirements of 
>> the NameNode.
>>
>> --Dan
>>
>> --
>>
>> Daniel Washburn
>> Systems Engineer
>> Explorys, Inc.
>> [email protected]
>

Reply via email to