[
https://issues.apache.org/jira/browse/HBASE-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191638#comment-13191638
]
Hudson commented on HBASE-5243:
-------------------------------
Integrated in HBase-0.92 #258 (See
[https://builds.apache.org/job/HBase-0.92/258/])
HBASE-5243 Addendum moves the close() method to right place
tedyu :
Files :
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLog.java
> LogSyncerThread not getting shutdown waiting for the interrupted flag
> ---------------------------------------------------------------------
>
> Key: HBASE-5243
> URL: https://issues.apache.org/jira/browse/HBASE-5243
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.5
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 0.90.6, 0.92.1
>
> Attachments: 5243-92.addendum, HBASE-5243_0.90.patch,
> HBASE-5243_0.90_1.patch, HBASE-5243_trunk.patch
>
>
> In the LogSyncer run() we keep looping till this.isInterrupted flag is set.
> But in some cases the DFSclient is consuming the Interrupted exception. So
> we are running into infinite loop in some shutdown cases.
> I would suggest that as we are the ones who tries to close down the
> LogSyncerThread we can introduce a variable like
> Close or shutdown and based on the state of this flag along with
> isInterrupted() we can make the thread stop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
