[
https://issues.apache.org/jira/browse/HBASE-12785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261364#comment-14261364
]
stack edited comment on HBASE-12785 at 12/30/14 7:07 PM:
---------------------------------------------------------
bq. I am working on a patch.
Good. I won't close this as friviolous just yet (What I don't get is that if
you are working on it 'now', why did HBASE-12607 have to get committed before
addressing Seans' comment rather than wait? Why create a JIRA just to address
his comment?)
was (Author: stack):
bq. I am working on a patch.
Good. I won't close this as friviolous just yet.
> Use FutureTask to timeout the attempt to get the lock for hbck
> --------------------------------------------------------------
>
> Key: HBASE-12785
> URL: https://issues.apache.org/jira/browse/HBASE-12785
> Project: HBase
> Issue Type: Task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
>
> In reviewing HBASE-12607, Sean pointed out:
> It would be nice if we used a
> [FutureTask|http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/FutureTask.html]
> to timeout the attempt to get the lock rather than wait the whole period and
> then fail.
> This issue is to address Sean's review comment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
