aboutsummaryrefslogtreecommitdiff
path: root/launcher
diff options
context:
space:
mode:
authorMark Grover <mark@apache.org>2016-07-27 10:13:15 -0700
committerMarcelo Vanzin <vanzin@cloudera.com>2016-07-27 10:13:15 -0700
commit70f846a313061e4db6174e0dc6c12c8c806ccf78 (patch)
tree9b8d7aa2edbd6af395b3b7b212252126cc1bf0e6 /launcher
parent7e8279fde176b08687adf2b410693b35cfbd4b46 (diff)
downloadspark-70f846a313061e4db6174e0dc6c12c8c806ccf78.tar.gz
spark-70f846a313061e4db6174e0dc6c12c8c806ccf78.tar.bz2
spark-70f846a313061e4db6174e0dc6c12c8c806ccf78.zip
[SPARK-5847][CORE] Allow for configuring MetricsSystem's use of app ID to namespace all metrics
## What changes were proposed in this pull request? Adding a new property to SparkConf called spark.metrics.namespace that allows users to set a custom namespace for executor and driver metrics in the metrics systems. By default, the root namespace used for driver or executor metrics is the value of `spark.app.id`. However, often times, users want to be able to track the metrics across apps for driver and executor metrics, which is hard to do with application ID (i.e. `spark.app.id`) since it changes with every invocation of the app. For such use cases, users can set the `spark.metrics.namespace` property to another spark configuration key like `spark.app.name` which is then used to populate the root namespace of the metrics system (with the app name in our example). `spark.metrics.namespace` property can be set to any arbitrary spark property key, whose value would be used to set the root namespace of the metrics system. Non driver and executor metrics are never prefixed with `spark.app.id`, nor does the `spark.metrics.namespace` property have any such affect on such metrics. ## How was this patch tested? Added new unit tests, modified existing unit tests. Author: Mark Grover <mark@apache.org> Closes #14270 from markgrover/spark-5847.
Diffstat (limited to 'launcher')
0 files changed, 0 insertions, 0 deletions