I run the yarn log command and got the following:
A set of yarnAllocator warnings 'expected to find requests, but found none.'
Then an error:
Akka. ErrorMonitor: associationError ...
But then I still get final app status: Succeeded, exit code 0
What does these errors mean?
On Wed, 16 Dec 2015 at 0
But what if I don't have more memory?
On Wed, 16 Dec 2015 at 08:13 Zhan Zhang wrote:
> There are two cases here. If the container is killed by yarn, you can
> increase jvm overhead. Otherwise, you have to increase the executor-memory
> if there is no memory leak happening.
>
> Thanks.
>
> Zhan Zh
There are two cases here. If the container is killed by yarn, you can increase
jvm overhead. Otherwise, you have to increase the executor-memory if there is
no memory leak happening.
Thanks.
Zhan Zhang
On Dec 15, 2015, at 9:58 PM, Eran Witkon
mailto:eranwit...@gmail.com>> wrote:
If the probl
If the problem is containers trying to use more memory then they allowed,
how do I limit them? I all ready have executor-memory 5G
Eran
On Tue, 15 Dec 2015 at 23:10 Zhan Zhang wrote:
> You should be able to get the logs from yarn by “yarn logs -applicationId
> xxx”, where you can possible find th
You should be able to get the logs from yarn by “yarn logs -applicationId xxx”,
where you can possible find the cause.
Thanks.
Zhan Zhang
On Dec 15, 2015, at 11:50 AM, Eran Witkon wrote:
> When running
> val data = sc.wholeTextFile("someDir/*") data.count()
>
> I get numerous warning from y
The most common reason is yarn is killing containers as containers are
trying to use more memory than they are allowed to. Please try bumping it up
On 16 Dec 2015 06:50, "Eran Witkon" wrote:
> When running
> val data = sc.wholeTextFile("someDir/*") data.count()
>
> I get numerous warning from yar
