You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by Billy <sa...@pearsonwholesale.com> on 2008/01/19 20:59:29 UTC
Hbase FATAL error
I been getting these errors from time to time seams like when the region
servers are under a load for long time they start failing with this error.
nit all at the same time but it happens on different servers. I know this is
not an network problem as one of the region servers is on the same node as
the master.
2008-01-19 11:07:17,637 FATAL org.apache.hadoop.hbase.HRegionServer: unable
to report to master for 33730 milliseconds - aborting server
Billy
Re: Hbase FATAL error
Posted by stack <st...@duboce.net>.
HADOOP-2343 describes regionservers 'hanging' inexplicably. Do you
think you are experiencing a similar phenomenon?
St.Ack
Billy wrote:
> I thank it might be related to something in the region server as it never
> happens to more then one region at a time but they all have failed over time
> even the one on the same node as the master so that rules out network/switch
> problems. if it was the master then all the regions server would go down at
> about the same time.
>
> Billy
>
> "stack" <st...@duboce.net> wrote in message
> news:4792585A.3060306@duboce.net...
>
>> regionservers will shut themselves down if they are unable to contact the
>> master. Can you figure what the master was doing such that it became
>> non-responsive during this time?
>> St.Ack
>>
>> Billy wrote:
>>
>>> I been getting these errors from time to time seams like when the region
>>> servers are under a load for long time they start failing with this
>>> error. nit all at the same time but it happens on different servers. I
>>> know this is not an network problem as one of the region servers is on
>>> the same node as the master.
>>>
>>> 2008-01-19 11:07:17,637 FATAL org.apache.hadoop.hbase.HRegionServer:
>>> unable to report to master for 33730 milliseconds - aborting server
>>>
>>> Billy
>>>
>>>
>>>
>>>
>>>
>>
>
>
>
>
Re: Hbase FATAL error
Posted by Billy <sa...@pearsonwholesale.com>.
I thank it might be related to something in the region server as it never
happens to more then one region at a time but they all have failed over time
even the one on the same node as the master so that rules out network/switch
problems. if it was the master then all the regions server would go down at
about the same time.
Billy
"stack" <st...@duboce.net> wrote in message
news:4792585A.3060306@duboce.net...
> regionservers will shut themselves down if they are unable to contact the
> master. Can you figure what the master was doing such that it became
> non-responsive during this time?
> St.Ack
>
> Billy wrote:
>> I been getting these errors from time to time seams like when the region
>> servers are under a load for long time they start failing with this
>> error. nit all at the same time but it happens on different servers. I
>> know this is not an network problem as one of the region servers is on
>> the same node as the master.
>>
>> 2008-01-19 11:07:17,637 FATAL org.apache.hadoop.hbase.HRegionServer:
>> unable to report to master for 33730 milliseconds - aborting server
>>
>> Billy
>>
>>
>>
>>
>
>
Re: Hbase FATAL error
Posted by stack <st...@duboce.net>.
regionservers will shut themselves down if they are unable to contact
the master. Can you figure what the master was doing such that it
became non-responsive during this time?
St.Ack
Billy wrote:
> I been getting these errors from time to time seams like when the region
> servers are under a load for long time they start failing with this error.
> nit all at the same time but it happens on different servers. I know this is
> not an network problem as one of the region servers is on the same node as
> the master.
>
> 2008-01-19 11:07:17,637 FATAL org.apache.hadoop.hbase.HRegionServer: unable
> to report to master for 33730 milliseconds - aborting server
>
> Billy
>
>
>
>