You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/07/01 20:18:00 UTC

[jira] [Closed] (HBASE-14015) Allow setting a richer state value when toString a pv2

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

Andrew Kyle Purtell closed HBASE-14015.
---------------------------------------

> Allow setting a richer state value when toString a pv2
> ------------------------------------------------------
>
>                 Key: HBASE-14015
>                 URL: https://issues.apache.org/jira/browse/HBASE-14015
>             Project: HBase
>          Issue Type: Improvement
>          Components: proc-v2
>            Reporter: Michael Stack
>            Assignee: Michael Stack
>            Priority: Minor
>             Fix For: 1.2.0, 1.3.0, 2.0.0
>
>         Attachments: 0001-HBASE-14015-Allow-setting-a-richer-state-value-when-.patch, 14015.addendum.to.fix.compile.issue.on.branch-1.branch-1.2.txt
>
>
> Debugging, my procedure after a crash was loaded out of the store and its state was RUNNING. It would help if I knew in which of the states of a StateMachineProcedure it was going to start RUNNING at.
> Chatting w/ Matteo, he suggested allowing Procedures customize the String.
> Here is patch that makes it so StateMachineProcedure will now print out the base state -- RUNNING, FINISHED -- followed by a ':' and then the StateMachineProcedure state: e.g. SimpleStateMachineProcedure state=RUNNABLE:SERVER_CRASH_ASSIGN



--
This message was sent by Atlassian Jira
(v8.20.10#820010)