Thanks a lot Thomas & Sandesh.
I somehow missed the "troubleshooting" section of the docs. This is what I
was looking for.
Regards,
Ananth
On Fri, May 13, 2016 at 1:30 AM, Thomas Weise
wrote:
> Ananth,
>
> Please have a look at:
>
> http://docs.datatorrent.com/troubleshooting/#configuring-mem
Ananth,
Please have a look at:
http://docs.datatorrent.com/troubleshooting/#configuring-memory
Thanks,
Thomas
On Thu, May 12, 2016 at 4:00 AM, Ananth Gundabattula <
agundabatt...@gmail.com> wrote:
> Thanks Shubham. I shall bump up the memory a bit more.
>
> I was wondering how the operator me
Yes, that's correct.
Also, there are other things that affects the container size as well,
examples: Unifiers, Max memory and Min memory.
If you are adventurous take look at the Physical Plan preparation code.
https://github.com/apache/incubator-apex-core/blob/ddb7471edd37ef228432c7d80e1e118368e6
Thanks Shubham. I shall bump up the memory a bit more.
I was wondering how the operator memory relates to the YARN container
memory settings ? Or it depends on the deployment models ?
For example , if the deployment model is thread local, the YARN container
needs to be ( considering above example
Hello Ananth,
Looks like operator requires more memory.
You may add this property to have more memory allocated to the container.
In properties.xml , for operator O in the application you may specify the
property :
dt.operator.*O*.attr.MEMORY_MB
2048
Thanks,
Shubham
On Thu, May 12, 2016 at
Hello All,
I am seeing the following log from the web ui ocassionally when my
operators are getting killed. Is there any way I can control the memory
settings that are used to communicate with YARN when negotiating a
container ?
How does the typical yarn settings for a container heap and max mem
