hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allan Yang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-21423) Procedures for meta table/region should be able to execute in separate workers
Date Mon, 12 Nov 2018 02:49:00 GMT

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

Allan Yang resolved HBASE-21423.
    Resolution: Fixed

Opened HBASE-21468 for the addendum, close this one

> 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, HBASE-21423.branch-2.0.addendum.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

View raw message