hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18106) Redo ProcedureInfo and LockInfo
Date Wed, 05 Jul 2017 22:47:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075571#comment-16075571
] 

stack commented on HBASE-18106:
-------------------------------

Perhaps graphs could be done with a d3 lib if we had an API that gave out JSON versions of
procedure info and lock info.

> Redo ProcedureInfo and LockInfo
> -------------------------------
>
>                 Key: HBASE-18106
>                 URL: https://issues.apache.org/jira/browse/HBASE-18106
>             Project: HBase
>          Issue Type: Sub-task
>          Components: proc-v2
>    Affects Versions: 2.0.0
>            Reporter: stack
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> ProcedureInfo was introduced as a lowest-common-denominator POJO that could be used as
a facade on PB Procedures. It was good for showing state of Procedure framework in shell and
UI.
> Its a bit weird though. Its up in hbase-common rather than in Procedure and it can only
ever show a subset of the Procedure info.
> I was thinking we could use the pb3.1 pb->JSON utility instead and emit a JSON String
wherever we need to export a view on procedure internals.
> This issue is about exploring this possibility. Would depend on our having an upgraded
guava (so probably depends on the 'pre-build' project).
> From ProcedureInfo and LockInfo need fixing in https://docs.google.com/document/d/1eVKa7FHdeoJ1-9o8yZcOTAQbv0u0bblBlCCzVSIn69g/edit#heading=h.kid1jzo114xw



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message