[
https://issues.apache.org/jira/browse/HBASE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973473#action_12973473
]
stack commented on HBASE-3343:
------------------------------
Oh, I forgot, here are the snippets from Todd's log that show fsok being set to
false followed by the abort processing:
{code}
12596 2010-12-13 11:43:46,460 FATAL
org.apache.hadoop.hbase.regionserver.HRegionServer: ABORTING region server
serverName=haus03.sf.cloudera.com,60020,1292269332749, load=(requests=894,
regions=6, usedHeap=2039, maxHeap=8185): File System not available
12597 java.io.IOException: File system is not available
....
17936 2010-12-13 11:43:46,535 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: aborting server at:
haus03.sf.cloudera.com,60020,1292269332749
{code}
> Server not shutting down after losing log lease
> -----------------------------------------------
>
> Key: HBASE-3343
> URL: https://issues.apache.org/jira/browse/HBASE-3343
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.0
> Reporter: Todd Lipcon
> Assignee: stack
> Priority: Critical
> Fix For: 0.90.0
>
> Attachments: HBASE-3343.patch, shutdown-logs.txt.bz2, stuck-server.txt
>
>
> Ran into this bug testing 0.90rc2. I kill -STOPed a server, and then -CONT it
> after its logs had been split. It correctly decided it should abort, but got
> stuck during the shutdown process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
