[jira] [Commented] (HBASE-18106) Redo ProcedureInfo and LockInfo

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on HBASE-18106:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  5s{color} | {color:red} HBASE-18106 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-18106 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12881473/HBASE-18106.master.002.patch |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/8038/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> 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, 3.0.0
>
>         Attachments: HBASE-18106.master.001.patch, HBASE-18106.master.002.patch
>
>
> 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)