Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add metrics definition link to tool README.md[skip ci] #2787

Merged
merged 7 commits into from
Jun 29, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update tools/README.md
Co-authored-by: Sameer Raheja <sameerz@users.noreply.github.com>
nvliyuan and sameerz authored Jun 28, 2021

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
commit f20b6024d6087f44f238cf8b88961b37bbb0c45f
3 changes: 1 addition & 2 deletions tools/README.md
Original file line number Diff line number Diff line change
@@ -431,7 +431,7 @@ Failed jobs:
```

### Metrics Definitions
All the metrics definition can be found in [executor task metrics doc](https://spark.apache.org/docs/latest/monitoring.html#executor-task-metrics) / [executor metrics doc](https://spark.apache.org/docs/latest/monitoring.html#executor-metrics) or [SPARK webUI doc](https://spark.apache.org/docs/latest/web-ui.html#content).
All the metrics definitions can be found in the [executor task metrics doc](https://spark.apache.org/docs/latest/monitoring.html#executor-task-metrics) / [executor metrics doc](https://spark.apache.org/docs/latest/monitoring.html#executor-metrics) or the [SPARK webUI doc](https://spark.apache.org/docs/latest/web-ui.html#content).

### How to use this tool
This tool parses the Spark CPU or GPU event log(s) and creates an output report.
@@ -508,4 +508,3 @@ The output location can be changed using the `--output-directory` option. Defaul
Note: We suggest you also save the output of the `spark-submit` or `spark-shell` to a log file for troubleshooting.

Run `--help` for more information.