[
https://issues.apache.org/jira/browse/HBASE-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617208#action_12617208
]
stack commented on HBASE-776:
-----------------------------
This exception of yours Andrew seems pretty easy to manufacture. I see it here
in a little test I'm running. Kept getting the exception over and over for 30
mins now.
{code}
2008-07-26 19:09:22,111 WARN org.apache.hadoop.hbase.master.BaseScanner: Scan
one META region: {regionname: .META.,,1, startKey: <>, server:
XX.XX.XX.XX:60020}
java.net.SocketTimeoutException: timed out waiting for rpc response
at org.apache.hadoop.ipc.Client.call(Client.java:559)
at
org.apache.hadoop.hbase.ipc.HbaseRPC$Invoker.invoke(HbaseRPC.java:230)
at $Proxy2.openScanner(Unknown Source)
at
org.apache.hadoop.hbase.master.BaseScanner.scanRegion(BaseScanner.java:159)
at
org.apache.hadoop.hbase.master.MetaScanner.scanOneMetaRegion(MetaScanner.java:69)
at
org.apache.hadoop.hbase.master.MetaScanner.maintenanceScan(MetaScanner.java:124)
at
org.apache.hadoop.hbase.master.BaseScanner.chore(BaseScanner.java:139)
at org.apache.hadoop.hbase.Chore.run(Chore.java:63)
{code}
> Master not reassigning .META. from failed/failing regionserver
> --------------------------------------------------------------
>
> Key: HBASE-776
> URL: https://issues.apache.org/jira/browse/HBASE-776
> Project: Hadoop HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.2.0
> Environment: CentOS x86_64, JDK 1.6, Hadoop 0.17.1, HBase 0.2.0,
> r679585, Fri Jul 25 16:47:26 UTC 2008
> Reporter: Andrew Purtell
> Attachments: hbase-hadoop-master-sjdc-atr-dc-1.log,
> hbase-hadoop-regionserver-sjdc-atr-dc-13.log, master_gui.png
>
>
> In our environment sometimes the regionserver carrying META is also assigned
> to the 'content' table, into which objects retrieved from Internet crawling
> is stored. For unclear reason the regionserver occasionally goes "deaf"
> (seperate issue) and when this happens META is no longer available. The
> master then never reassigns META, so the whole cluster is down from this
> point and does not recover. Logs attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
