You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Appy (JIRA)" <ji...@apache.org> on 2017/01/25 20:28:26 UTC
[jira] [Updated] (HBASE-17537) Remove Queue#isAvailable() since we
have waits/wakes after HBASE-17067
[ https://issues.apache.org/jira/browse/HBASE-17537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Appy updated HBASE-17537:
-------------------------
Description:
Earlier, run-queues could have empty queues or queues for which exclusive locks are already taken. Thus poll() on table/server run-queue might have returned a Queue which didn't have any valid procs to run.
With wait/wake on exclusive locks doing {removeFrom|addTo}RunQueue and poll removing queues when last element is removed, i think we can remove this function now.
(am finding these things when working on a larger patch, but there are changes like this which seem too critical to mess up, so am creating smaller focused patches for them).
> Remove Queue#isAvailable() since we have waits/wakes after HBASE-17067
> ----------------------------------------------------------------------
>
> Key: HBASE-17537
> URL: https://issues.apache.org/jira/browse/HBASE-17537
> Project: HBase
> Issue Type: Sub-task
> Components: master, proc-v2
> Reporter: Appy
> Assignee: Appy
> Priority: Minor
> Fix For: 2.0.0
>
>
> Earlier, run-queues could have empty queues or queues for which exclusive locks are already taken. Thus poll() on table/server run-queue might have returned a Queue which didn't have any valid procs to run.
> With wait/wake on exclusive locks doing {removeFrom|addTo}RunQueue and poll removing queues when last element is removed, i think we can remove this function now.
> (am finding these things when working on a larger patch, but there are changes like this which seem too critical to mess up, so am creating smaller focused patches for them).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)