You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@carbondata.apache.org by "Ravindra Pesala (JIRA)" <ji...@apache.org> on 2017/06/08 10:35:18 UTC

[jira] [Resolved] (CARBONDATA-1133) Executor lost failure in case of data load failure due to bad records

     [ https://issues.apache.org/jira/browse/CARBONDATA-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ravindra Pesala resolved CARBONDATA-1133.
-----------------------------------------
    Resolution: Fixed

> Executor lost failure in case of data load failure due to bad records
> ---------------------------------------------------------------------
>
>                 Key: CARBONDATA-1133
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-1133
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: Manish Gupta
>            Assignee: Manish Gupta
>             Fix For: 1.2.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> when we try to do data load with bad records continuously, after some time it is observed that executor is lost due to OOM error and application also gets restarted by yarn after some time. This happens because in case of data load failure due to bad records exception is thrown by the executor and task keeps retrying till the max number of retry attempts are reached. This keeps happening continuously and after some time application is restarted by yarn.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)