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

Hudson commented on HBASE-26986:
--------------------------------

Results for branch branch-2.5
        [build #121 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/121/]:
 (/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/121/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/121/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/121/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/121/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Trace a one-shot execution of a Master procedure
> ------------------------------------------------
>
>                 Key: HBASE-26986
>                 URL: https://issues.apache.org/jira/browse/HBASE-26986
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.5.0, 3.0.0-alpha-2
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-3
>
>
> A self-contained effort towards wrangling the stray traces identified in 
> HBASE-26366. This one adds a tracing context to the Master's ProcedureV2 
> execution. This ties all the spans that result from a procedure execution 
> back to a procedure by name.
> Maybe in a follow-on issue, we can serialize span context along with 
> procedures and display procedure start/stop/retry events and parent-child 
> hierarchy in tracing visualization.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to