hbase/conf
Nick Dimiduk a238ed2785
HBASE-27182 Rework tracing configuration
* 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>
2022-07-11 14:37:05 +02:00
..
hadoop-metrics2-hbase.properties HBASE-14087 Ensure correct ASF headers for docs/code 2015-07-29 14:25:43 -05:00
hbase-env.cmd HBASE-26723 Switch to use log4j2.properties file to configure log4j2 (#4096) 2022-03-02 21:08:32 +08:00
hbase-env.sh HBASE-27182 Rework tracing configuration 2022-07-11 14:37:05 +02:00
hbase-policy.xml HBASE-26899 Run spotless:apply 2022-05-01 22:15:09 +08:00
hbase-site.xml HBASE-24271 Set values in `conf/hbase-site.xml` that enable running on `LocalFileSystem` out of the box 2020-05-14 13:18:43 -07:00
log4j2-hbtop.properties HBASE-26723 Switch to use log4j2.properties file to configure log4j2 (#4096) 2022-03-02 21:08:32 +08:00
log4j2.properties HBASE-26723 Switch to use log4j2.properties file to configure log4j2 (#4096) 2022-03-02 21:08:32 +08:00
regionservers HBASE-12034 If I kill single RS in branch-1, all regions end up on Master! 2014-09-29 13:50:59 -07:00