Yup, I just noticed it's there :-)

tx,
Harry


On 12 February 2016 at 20:38, Kamil Chmielewski <[email protected]> wrote:

> 2016-02-12 19:41 GMT+01:00 Erik Weathers <[email protected]>:
>
>> hey Harry,
>>
>> As Vinod said, the mesos-slave/agent will issue a status update about the
>> OOM condition.  This will be received by the scheduler of the framework.
>> In the storm-mesos framework we just log the messages (see below), but you
>> might consider somehow exposing these messages directly to the app owners:
>>
>> Received status update:
>> {"task_id":"TASK_ID","slave_id":"20150806-001422-1801655306-5050-22041-S65","state":"TASK_FAILED","message":"Memory
>> limit exceeded: Requested: 2200MB Maximum Used: 2200MB\n\nMEMORY
>> STATISTICS: \ncache 20480\nrss 1811943424\nmapped_file 0\npgpgin
>> 8777434\npgpgout 8805691\nswap 96878592\ninactive_anon
>> 644186112\nactive_anon 1357594624\ninactive_file 20480\nactive_file
>> 0\nunevictable 0\nhierarchical_memory_limit
>> 2306867200\nhierarchical_memsw_limit 9223372036854775807\ntotal_cache
>> 20480\ntotal_rss 1811943424\ntotal_mapped_file 0\ntotal_pgpgin
>> 8777434\ntotal_pgpgout 8805691\ntotal_swap 96878592\ntotal_inactive_anon
>> 644186112\ntotal_active_anon 1355497472\ntotal_inactive_file
>> 20480\ntotal_active_file 0\ntotal_unevictable 0"}
>>
>> -
>>
>
> Marathon also presents this information. Developers will see it on Debug
> tab in Last Task Failure Section.
>
> Best Regards,
> Kamil
>

Reply via email to