Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
1.6.0
-
None
Description
Currently Spark automatically sets the -Xms parameter to be the same as the -Xmx parameter. We should allow the user to set this separately.
The main use case here is if I'm running the spark-shell on a shared gateway. Many users specify a larger memory size then needed and will never use that much memory, so all its doing is preventing other users from potentially using that memory. Allowing it to be less is just more multi-tenant friendly.
I think it makes sense to leave this for cluster mode, although if a user really wants to override I don't see why we shouldn't let them.
Attachments
Issue Links
- is related to
-
SPARK-16320 Document G1 heap region's effect on spark 2.0 vs 1.6
- Resolved
- links to