Skip to content

[SPARK-32119][FOLLOWUP][DOC] Update monitoring doc following the improvement in SPARK-32119 #29463

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.

Sign up for GitHub

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

Closed
LucaCanali wants to merge 1 commit into from
Closed

[SPARK-32119][FOLLOWUP][DOC] Update monitoring doc following the improvement in SPARK-32119 #29463

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 0 additions & 6 deletions docs/monitoring.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1366,9 +1366,3 @@ Both take a comma-separated list of class names that implement the
possible for one list to be placed in the Spark default config file, allowing users to
easily add other plugins from the command line without overwriting the config file's list. Duplicate
plugins are ignored.

Distribution of the jar files containing the plugin code is currently not done by Spark. The user
or admin should make sure that the jar files are available to Spark applications, for example, by
including the plugin jar with the Spark distribution. The exception to this rule is the YARN
backend, where the <code>--jars</code> command line option (or equivalent config entry) can be
used to make the plugin code available to both executors and cluster-mode drivers.