Repository: carbondata Updated Branches: refs/heads/master 8034949e5 -> 366415691
[Documentation] FAQ added for Why all executors are showing success in Spark UI even after Dataload command failed at Driver side? FAQ added for Why are all executors showing success in Spark UI even after Dataload command failed at Driver side? This closes #2183 Project: http://git-wip-us.apache.org/repos/asf/carbondata/repo Commit: http://git-wip-us.apache.org/repos/asf/carbondata/commit/36641569 Tree: http://git-wip-us.apache.org/repos/asf/carbondata/tree/36641569 Diff: http://git-wip-us.apache.org/repos/asf/carbondata/diff/36641569 Branch: refs/heads/master Commit: 366415691acb69860885e66afea498d6ba07efd4 Parents: 8034949 Author: sgururajshetty <[email protected]> Authored: Wed Apr 18 17:08:05 2018 +0530 Committer: KanakaKumar <[email protected]> Committed: Thu Apr 19 11:30:40 2018 +0530 ---------------------------------------------------------------------- docs/faq.md | 3 +++ 1 file changed, 3 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/carbondata/blob/36641569/docs/faq.md ---------------------------------------------------------------------- diff --git a/docs/faq.md b/docs/faq.md index b5f8254..a2f8f59 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -26,6 +26,7 @@ * [How to resolve Abstract Method Error?](#how-to-resolve-abstract-method-error) * [How Carbon will behave when execute insert operation in abnormal scenarios?](#how-carbon-will-behave-when-execute-insert-operation-in-abnormal-scenarios) * [Why aggregate query is not fetching data from aggregate table?](#why-aggregate-query-is-not-fetching-data-from-aggregate-table) +* [Why all executors are showing success in Spark UI even after Dataload command failed at Driver side?](#Why-all-executors-are-showing-success-in-Spark-UI-even-after-Dataload-command-failed-at-driver-side) ## What are Bad Records? Records that fail to get loaded into the CarbonData due to data type incompatibility or are empty or have incompatible format are classified as Bad Records. @@ -178,4 +179,6 @@ create datamap ag1 on table gdp21 using 'preaggregate' as select cntry, sum(gdp) select cntry,sum(gdp) from gdp21,pop1 where cntry=ctry group by cntry; ``` +## Why all executors are showing success in Spark UI even after Dataload command failed at Driver side? +Spark executor shows task as failed after the maximum number of retry attempts, but loading the data having bad records and BAD_RECORDS_ACTION (carbon.bad.records.action) is set as âFAILâ will attempt only once but will send the signal to driver as failed instead of throwing the exception to retry, as there is no point to retry if bad record found and BAD_RECORDS_ACTION is set to fail. Hence the Spark executor displays this one attempt as successful but the command has actually failed to execute. Task attempts or executor logs can be checked to observe the failure reason.
