a238ed2785
* 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. DRY up tracing configuration and make it easier to manage in a container environment. * Replace `HBASE_TRACE_OPTS`, which used to act as both a feature flag and a baseline for configuration shared across processes. Instead, use `HBASE_OTEL_TRACING_ENABLED` as a feature flag, and let configuration reuse be handled via the environment variables that otel supports naively. * Add further explanation for how to write your configuration for our different deployment modes (standalone, pseudo-distributed, fully distributed) and in different environments. Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Andrew Purtell <apurtell@apache.org> |
||
|---|---|---|
| .. | ||
| hadoop-metrics2-hbase.properties | ||
| hbase-env.cmd | ||
| hbase-env.sh | ||
| hbase-policy.xml | ||
| hbase-site.xml | ||
| log4j2-hbtop.properties | ||
| log4j2.properties | ||
| regionservers | ||