ODIn/spark-instrumented-optimizer
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[SPARK-34911][SQL] Fix code not close issue in monitoring.md

Browse source 
### What changes were proposed in this pull request?
Fix code not close issue in monitoring.md

### Why are the changes needed?
Fix doc issue

### Does this PR introduce _any_ user-facing change?
No

### How was this patch tested?
Not need

Closes #32008 from AngersZhuuuu/SPARK-34911.

Authored-by: Angerszhuuuu <angers.zhu@gmail.com>
Signed-off-by: Sean Owen <srowen@gmail.com>
This commit is contained in:
Angerszhuuuu 2021-03-31 02:55:08 -05:00 committed by Sean Owen
parent f05b940749
commit 1c3bdabc03
1 changed files with 5 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/monitoring.md
View file

@ -479,14 +479,13 @@ can be identified by their `[attempt-id]`. In the API listed below, when running
<td><code>/applications/[app-id]/stages/[stage-id]</code></td>
<td>
A list of all attempts for the given stage.
<br><code>?details=true</code> lists all attempts with task data for the given stage.
<br><code>?taskStatus=[RUNNING|SUCCESS|FAILED|KILLED|PENDING]</code> lists only those tasks with the specified task status. Query parameter taskStatus takes effect only when <code>details=true</code>.
<br><code>?details=true</code> lists all attempts with the task data for the given stage.
<br><code>?taskStatus=[RUNNING|SUCCESS|FAILED|KILLED|PENDING]</code> lists only those tasks with the specified task status. Query parameter taskStatus takes effect only when <code>details=true</code>.
<br><code>?withSummaries=true</code> lists task metrics distribution and executor metrics distribution of each attempt.
<br><code>?quantiles=0.1,0.25,0.5,0.75,1.0</code> summarize the metrics with the given quantiles. Query parameter quantiles takes effect only when <code>withSummaries=true</code>. Default value is <code>0.0,0.25,0.5,0.75,1.0</code>.
<br><code>?quantiles=0.0,0.25,0.5,0.75,1.0</code> summarize the metrics with the given quantiles. Query parameter quantiles takes effect only when <code>withSummaries=true</code>. Default value is <code>0.0,0.25,0.5,0.75,1.0</code>.
<br>Example:
<br><code>?details=true</code>
<br><code>?details=true&taskStatus=RUNNING<code>
<br><code>?details=true&taskStatus=RUNNING</code>
<br><code>?withSummaries=true</code>
<br><code>?details=true&withSummaries=true&quantiles=0.01,0.5,0.99</code>
</td>
@ -498,10 +497,10 @@ can be identified by their `[attempt-id]`. In the API listed below, when running
<br><code>?details=true</code> lists all task data for the given stage attempt.
<br><code>?taskStatus=[RUNNING|SUCCESS|FAILED|KILLED|PENDING]</code> lists only those tasks with the specified task status. Query parameter taskStatus takes effect only when <code>details=true</code>.
<br><code>?withSummaries=true</code> lists task metrics distribution and executor metrics distribution for the given stage attempt.
<br><code>?quantiles=0.1,0.25,0.5,0.75,1.0</code> summarize the metrics with the given quantiles. Query parameter quantiles takes effect only when <code>withSummaries=true</code>. Default value is <code>0.0,0.25,0.5,0.75,1.0</code>.
<br><code>?quantiles=0.0,0.25,0.5,0.75,1.0</code> summarize the metrics with the given quantiles. Query parameter quantiles takes effect only when <code>withSummaries=true</code>. Default value is <code>0.0,0.25,0.5,0.75,1.0</code>.
<br>Example:
<br><code>?details=true</code>
<br><code>?details=true&taskStatus=RUNNING<code>
<br><code>?details=true&taskStatus=RUNNING</code>
<br><code>?withSummaries=true</code>
<br><code>?details=true&withSummaries=true&quantiles=0.01,0.5,0.99</code>
</td>