Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
spark
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
cs525-sp18-g07
spark
Commits
2dd4fb56
Commit
2dd4fb56
authored
11 years ago
by
Andrew Ash
Browse files
Options
Downloads
Patches
Plain Diff
Clarify spark.cores.max
It controls the count of cores across the cluster, not on a per-machine basis.
parent
a2e7e049
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/configuration.md
+2
-1
2 additions, 1 deletion
docs/configuration.md
with
2 additions
and
1 deletion
docs/configuration.md
+
2
−
1
View file @
2dd4fb56
...
@@ -81,7 +81,8 @@ there are at least five properties that you will commonly want to control:
...
@@ -81,7 +81,8 @@ there are at least five properties that you will commonly want to control:
<td>
<td>
When running on a
<a
href=
"spark-standalone.html"
>
standalone deploy cluster
</a>
or a
When running on a
<a
href=
"spark-standalone.html"
>
standalone deploy cluster
</a>
or a
<a
href=
"running-on-mesos.html#mesos-run-modes"
>
Mesos cluster in "coarse-grained"
<a
href=
"running-on-mesos.html#mesos-run-modes"
>
Mesos cluster in "coarse-grained"
sharing mode
</a>
, how many CPU cores to request at most. The default will use all available cores
sharing mode
</a>
, the maximum amount of CPU cores to request for the application from
across the cluster (not from each machine). The default will use all available cores
offered by the cluster manager.
offered by the cluster manager.
</td>
</td>
</tr>
</tr>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment