<p>TLDR; set workers' memory to 4G.</p>

<p>I reduced the test to the build-in Pi calculation:</p>

<pre><code>./bin/run-example SparkPi 10
</code></pre>

<p>And got the same result; apparently 1G memory is insufficient even for simplest experiments.
Increasing both master and workers memory to 4G and the problematic behaviour was not reproducible. However before the systems start computation the message still could appear but just once, seems it is printed in a waiting loop.</p>

CC BY-SA 3.0
2017-07-23T12:41:11.927Z
Does this answer the question or should this be part of the question?
030
CC BY-SA 3.0
2017-07-23T19:37:29.640Z
it's the answer
Ta Mu
CC BY-SA 3.0
2017-07-22T12:25:11.827Z
2017-07-23T19:37:11.643Z
2017-07-23T19:37:11.643Z
Ta Mu
<p>IMO the dashboard does not match the log error, or?</p>

<p>Spark master dashboard says (similar for memory as well):</p>

<blockquote>
  <p>Alive Workers: 2
  Cores in use: 2 Total, 0 Used</p>
</blockquote>

<p>Log:</p>

<pre><code>17/07/21 20:48:45 WARN TaskSchedulerImpl: Initial job has not accepted any 
resources; 
check your cluster UI to ensure that workers are registered 
and have sufficient resources
</code></pre>

<p>Assuming there was e.g. not enough memory, how to determine that? Maybe a symptom, the workers get here and now "dissociated" but then reconnect.</p>

CC BY-SA 3.0
2017-07-22T12:13:14.600Z
https://stackoverflow.com/q/35662596/2777965
030
<docker>
Spark on a Docker swarm - workers won't accept jobs
Ta Mu
# Spark on a Docker swarm - workers won't accept jobs

(Asked by: username_0 on 2017-07-21)

IMO the dashboard does not match the log error, or?
Spark master dashboard says (similar for memory as well):

Alive Workers: 2
  Cores in use: 2 Total, 0 Used

Log:
17/07/21 20:48:45 WARN TaskSchedulerImpl: Initial job has not accepted any 
resources; 
check your cluster UI to ensure that workers are registered 
and have sufficient resources

Assuming there was e.g. not enough memory, how to determine that? Maybe a symptom, the workers get here and now "dissociated" but then reconnect.

**Tags:** docker

> **Comments:**
> **username_1**: https://stackoverflow.com/q/35662596/2777965  

---

## 1 answers

### Answer by username_0 on 2017-07-22. Score: 0 | Accepted answer

TLDR; set workers' memory to 4G.
I reduced the test to the build-in Pi calculation:
./bin/run-example SparkPi 10

And got the same result; apparently 1G memory is insufficient even for simplest experiments.
Increasing both master and workers memory to 4G and the problematic behaviour was not reproducible. However before the systems start computation the message still could appear but just once, seems it is printed in a waiting loop.

> **Comments:**
> **username_1**: Does this answer the question or should this be part of the question?  
> **username_0**: it's the answer  

---

