[ 
https://issues.apache.org/jira/browse/SPARK-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

lichenglin updated SPARK-13433:
-------------------------------
    Description: 
I have a 16 cores cluster.
When I submit a lot of job to the standalone  server in cluster mode.
A  Running driver at least use 1 core may be more.
So all the cores may be used for running driver,
and then there is no cores to run applications
The server is stuck.
So I think we should limit the resources for running driver.



  was:
I have a 16 cores cluster.
When I submit a lot of job to the standalone  server in cluster mode.
A  Running driver at least use 1 core may be more.
So all the cores may be used for running driver,
and then there is no cores to run applications
The server is stuck.
So I think we should limit the cores for running driver.



        Summary: The standalone   server should limit the count of cores and 
memory for running Drivers  (was: The standalone   should limit the count of 
Running Drivers)

> The standalone   server should limit the count of cores and memory for 
> running Drivers
> --------------------------------------------------------------------------------------
>
>                 Key: SPARK-13433
>                 URL: https://issues.apache.org/jira/browse/SPARK-13433
>             Project: Spark
>          Issue Type: Improvement
>          Components: Scheduler
>    Affects Versions: 1.6.0
>            Reporter: lichenglin
>
> I have a 16 cores cluster.
> When I submit a lot of job to the standalone  server in cluster mode.
> A  Running driver at least use 1 core may be more.
> So all the cores may be used for running driver,
> and then there is no cores to run applications
> The server is stuck.
> So I think we should limit the resources for running driver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to