[
https://issues.apache.org/jira/browse/HBASE-14837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083729#comment-15083729
]
stack commented on HBASE-14837:
-------------------------------
Patch looks good on quick review.
bq. // TODO: should this be part of the HTD?
Not yet I'd say. Will only confuse till better baked.
This makes sense to me:
{code}
158 // For now, let server handling have precedence over table
handling; presumption is that it
159 // is more important handling crashed servers than it is running
the
160 // enabling/disabling tables, etc.
{code}
A ProcedureEvent could get in the way of both table and server events? I
suppose that makes sense. A ProcedureEvent is a major transition?
Whats this? AvlTree ?
> Procedure Queue Improvement
> ---------------------------
>
> Key: HBASE-14837
> URL: https://issues.apache.org/jira/browse/HBASE-14837
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2
> Affects Versions: 1.2.0, 1.1.2
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.2.1
>
> Attachments: HBASE-14837-v0.patch, HBASE-14837-v1.patch
>
>
> Add event support to the procedure queue to avoid spinning and remove all the
> immutable object creations from the java classes Map, Tree, ...
> the queues that can't be executed because are waiting for an event (e.g.
> master initialized) or someone else have an exclusive lock are pulled out the
> run queue
> https://reviews.apache.org/r/40460/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
