[SPARK-33397][YARN][DOC] Fix generating md to html for available-patterns-for-shs-custom-executor-log-url
### What changes were proposed in this pull request? 1. replace `{{}}` with `{{}}` 2. using `<code></code>` in td-tag ### Why are the changes needed? to fix this. ![image](https://user-images.githubusercontent.com/8326978/98544155-8c74bc00-22ce-11eb-8889-8dacb726b762.png) ### Does this PR introduce _any_ user-facing change? yes, you will see the correct online doc with this change ![image](https://user-images.githubusercontent.com/8326978/98545256-2e48d880-22d0-11eb-9dd9-b8cae3df8659.png) ### How was this patch tested? shown as the above pic via jekyll serve. Closes #30298 from yaooqinn/SPARK-33397. Authored-by: Kent Yao <yaooqinn@hotmail.com> Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
This commit is contained in:
parent
090962cd42
commit
036c11b0d4
|
@ -584,46 +584,46 @@ To use a custom metrics.properties for the application master and executors, upd
|
|||
<table class="table">
|
||||
<tr><th>Pattern</th><th>Meaning</th></tr>
|
||||
<tr>
|
||||
<td>{{HTTP_SCHEME}}</td>
|
||||
<td>`http://` or `https://` according to YARN HTTP policy. (Configured via `yarn.http.policy`)</td>
|
||||
<td>{{HTTP_SCHEME}}</td>
|
||||
<td><code>http://</code> or <code>https://</code> according to YARN HTTP policy. (Configured via <code>yarn.http.policy</code>)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>{{NM_HOST}}</td>
|
||||
<td>{{NM_HOST}}</td>
|
||||
<td>The "host" of node where container was run.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>{{NM_PORT}}</td>
|
||||
<td>{{NM_PORT}}</td>
|
||||
<td>The "port" of node manager where container was run.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>{{NM_HTTP_PORT}}</td>
|
||||
<td>{{NM_HTTP_PORT}}</td>
|
||||
<td>The "port" of node manager's http server where container was run.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>{{NM_HTTP_ADDRESS}}</td>
|
||||
<td>{{NM_HTTP_ADDRESS}}</td>
|
||||
<td>Http URI of the node on which the container is allocated.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>{{CLUSTER_ID}}</td>
|
||||
<td>The cluster ID of Resource Manager. (Configured via `yarn.resourcemanager.cluster-id`)</td>
|
||||
<td>{{CLUSTER_ID}}</td>
|
||||
<td>The cluster ID of Resource Manager. (Configured via <code>yarn.resourcemanager.cluster-id</code>)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>{{CONTAINER_ID}}</td>
|
||||
<td>{{CONTAINER_ID}}</td>
|
||||
<td>The ID of container.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>{{USER}}</td>
|
||||
<td>'SPARK_USER' on system environment.</td>
|
||||
<td>{{USER}}</td>
|
||||
<td><code>SPARK_USER</code> on system environment.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>{{FILE_NAME}}</td>
|
||||
<td>`stdout`, `stderr`.</td>
|
||||
<td>{{FILE_NAME}}</td>
|
||||
<td><code>stdout</code>, <code>stderr</code>.</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
For example, suppose you would like to point log url link to Job History Server directly instead of let NodeManager http server redirects it, you can configure `spark.history.custom.executor.log.url` as below:
|
||||
|
||||
`{{HTTP_SCHEME}}<JHS_HOST>:<JHS_PORT>/jobhistory/logs/{{NM_HOST}}:{{NM_PORT}}/{{CONTAINER_ID}}/{{CONTAINER_ID}}/{{USER}}/{{FILE_NAME}}?start=-4096`
|
||||
<code>{{HTTP_SCHEME}}<JHS_HOST>:<JHS_PORT>/jobhistory/logs/{{NM_HOST}}:{{NM_PORT}}/{{CONTAINER_ID}}/{{CONTAINER_ID}}/{{USER}}/{{FILE_NAME}}?start=-4096</code>
|
||||
|
||||
NOTE: you need to replace `<JHS_POST>` and `<JHS_PORT>` with actual value.
|
||||
|
||||
|
|
Loading…
Reference in a new issue