[jira] [Commented] (HBASE-27182) Rework tracing configuration

["Hudson (Jira)" <ji...@apache.org>]

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

Hudson commented on HBASE-27182:
--------------------------------

Results for branch branch-2
	[build #590 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/590/]: (/) *{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/590/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/590/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/590/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/590/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}


> Rework tracing configuration
> ----------------------------
>
>                 Key: HBASE-27182
>                 URL: https://issues.apache.org/jira/browse/HBASE-27182
>             Project: HBase
>          Issue Type: Task
>          Components: scripts
>    Affects Versions: 2.5.0, 2.6.0, 3.0.0-alpha-3
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-4
>
>
> I'd like to make some adjustments to how we manage tracing configuration in `conf/hbase-env.sh`. I'd like to take advantage of the fact that OpenTelemetry can read its configuration from environment variables and make use of this where possible, only falling back to passing properties into the process launch configuration when it's necessary. I think this will DRY up tracing configuration and make it easier to manage in a container environment.



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