[
https://issues.apache.org/jira/browse/HBASE-21423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675399#comment-16675399
]
Hudson commented on HBASE-21423:
--------------------------------
Results for branch branch-2.0
[build #1060 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1060/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1060//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1060//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1060//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Procedures for meta table/region should be able to execute in separate
> workers
> -------------------------------------------------------------------------------
>
> Key: HBASE-21423
> URL: https://issues.apache.org/jira/browse/HBASE-21423
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.1.1, 2.0.2
> Reporter: Allan Yang
> Assignee: Allan Yang
> Priority: Major
> Fix For: 2.0.3, 2.1.2
>
> Attachments: HBASE-21423.branch-2.0.001.patch,
> HBASE-21423.branch-2.0.002.patch, HBASE-21423.branch-2.0.003.patch
>
>
> We have higher priority for meta table procedures, but only in queue level.
> There is a case that the meta table is closed and a AssignProcedure(or RTSP
> in branch-2+) is waiting there to be executed, but at the same time, all the
> Work threads are executing procedures need to write to meta table, then all
> the worker will be stuck and retry for writing meta, no worker will take the
> AP for meta.
> Though we have a mechanism that will detect stuck and adding more
> ''KeepAlive'' workers to the pool to resolve the stuck. It is already stuck a
> long time.
> This is a real case I encountered in ITBLL.
> So, I add one 'Urgent work' to the ProceudureExecutor, which only take meta
> procedures(other workers can take meta procedures too), which can resolve
> this kind of stuck.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
