hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17537) Remove Queue#isAvailable() since we have waits/wakes after HBASE-17067
Date Sat, 03 Jun 2017 00:12:04 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-17537:
    Status: Patch Available  (was: Open)

See if it needed anywhere.

> 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
>         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

View raw message