[
https://issues.apache.org/jira/browse/HBASE-25423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558175#comment-17558175
]
Pankaj Kumar commented on HBASE-25423:
--------------------------------------
Intially I thought enable/disable/reset opentelemetry can be done using below
APIs,
{code}
GlobalOpenTelemetry#resetForTest()
GlobalOpenTelemetry.set(OpenTelemetry.noop());
{code}
But it seems, with opentelemetry javaagent it wont be the case. Currently we
uses the OpenTelemetry javaagent where AutoConfiguredOpenTelemetrySdk &
AgentListeners are initialized at the beginning. Since GlobalOpenTelemetry is a
singleton volatile instance, so runtime configuration change &
re-initialization will not be effective.
Also created discussion threads in OpenTelemetry,
https://github.com/open-telemetry/opentelemetry-java-instrumentation/discussions/5972
https://github.com/open-telemetry/community/discussions/1048
> Support dynamic update configurations about tracing, e.g. OpenTelemetry
> -----------------------------------------------------------------------
>
> Key: HBASE-25423
> URL: https://issues.apache.org/jira/browse/HBASE-25423
> Project: HBase
> Issue Type: Improvement
> Reporter: Xiaolin Ha
> Assignee: Xiaolin Ha
> Priority: Major
>
> It is necessary to update configurations which are relevant to HTrace without
> restart the RS, such as the sampler of HTrace.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
