You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2021/10/04 13:10:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17423932#comment-17423932 ]
Duo Zhang commented on HBASE-17537:
-----------------------------------
Any updates here? Is this still valid?
> 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: Bug
> Components: master, proc-v2
> Reporter: Apekshit Sharma
> Assignee: Apekshit Sharma
> Priority: Minor
> Attachments: HBASE-17537.master.001.patch, HBASE-17537.master.002.patch
>
>
> 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
(v8.3.4#803005)