hadoop-hdfs-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Krishna Kishore Bonagiri <write2kish...@gmail.com>
Subject Re: Yarn -- one of the daemons getting killed
Date Fri, 13 Dec 2013 12:52:51 GMT

  One more thing I observed is that, my Client which submits Application
Master one after another continuously also gets killed sometimes. So, it is
always any of the Java Processes that is getting killed. Does it indicate
some excessive memory usage by them or something like that, that is causing
them die? If so, how can we resolve this kind of issue?


On Fri, Dec 13, 2013 at 10:16 AM, Krishna Kishore Bonagiri <
write2kishore@gmail.com> wrote:

> No, I am running on 2 node cluster.
> On Fri, Dec 13, 2013 at 1:52 AM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
>> Is all of this on a single node?
>>  Thanks,
>> +Vinod
>> On Dec 12, 2013, at 3:26 AM, Krishna Kishore Bonagiri <
>> write2kishore@gmail.com> wrote:
>> Hi,
>>   I am running a small application on YARN (2.2.0) in a loop of 500
>> times, and while doing so one of the daemons, node manager, resource
>> manager, or data node is getting killed (I mean disappearing) at a random
>> point. I see no information in the corresponding log files. How can I know
>> why is it happening so?
>>  And, one more observation is that, this is happening only when I am
>> using "*" for node name in the container requests, otherwise when I used a
>> specific node name, everything is fine.
>> Thanks,
>> Kishore
>> NOTICE: This message is intended for the use of the individual or entity
>> to which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.

View raw message