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-15143) Procedure v2 - Web UI displaying queues
Date Tue, 25 Apr 2017 17:24:04 GMT

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

stack updated HBASE-15143:
      Resolution: Fixed
    Hadoop Flags: Reviewed
    Release Note: Adds a new Admin#listLocks, a panel on the procedures page to list procedure
locks, and a list_locks command to the shell. Use it to see current state of procedure locking
in Master process.
          Status: Resolved  (was: Patch Available)

Ran the failing tests locally and they pass for me. Need to figure why they fail so much on

Pushing since need this debugging.

Thanks [~balazs.meszaros] for persistence. Also, thanks for rebase. I was mangling it last

> Procedure v2 - Web UI displaying queues
> ---------------------------------------
>                 Key: HBASE-15143
>                 URL: https://issues.apache.org/jira/browse/HBASE-15143
>             Project: HBase
>          Issue Type: Sub-task
>          Components: proc-v2, UI
>            Reporter: Matteo Bertozzi
>            Assignee: Balazs Meszaros
>            Priority: Minor
>             Fix For: 2.0.0
>         Attachments: HBASE-15143-BM-0001.patch, HBASE-15143-BM-0002.patch, HBASE-15143-BM-0003.patch,
HBASE-15143-BM-0004.patch, HBASE-15143-BM-0005.patch, HBASE-15143-BM-0006.patch, HBASE-15143-BM-0006.patch,
HBASE-15143-BM-0006.patch, HBASE-15143-BM-0007.patch, HBASE-15143-BM-0008.patch, HBASE-15143-BM-0009.patch,
HBASE-15143-BM-0010.patch, HBASE-15143-BM-0011.patch, HBASE-15143-BM-0011.patch, HBASE-15143-BM-0012.patch,
> We can query MasterProcedureScheduler to display the various procedures and who is holding
table/region locks.
> Each procedure is in a TableQueue or ServerQueue, so it is easy to display the procedures
in its own group.

This message was sent by Atlassian JIRA

View raw message