Adding back user@spark
>From namenode audit log, you should be able to find out who deleted
part-r-00163-e94fa2c5-aa0d-4a08-b4c3-9fe7087ca493.gz.parquet and when.
There might be other errors in the executor log which would give you more
clue.
On Sun, May 15, 2016 at 9:08 AM, pseudo oduesp
wrote
bq. ExecutorLostFailure (executor 4 lost)
Can you check executor log for more clue ?
Which Spark release are you using ?
Cheers
On Sun, May 15, 2016 at 8:47 AM, pseudo oduesp
wrote:
> someone can help me about this issues
>
>
>
> py4j.protocol.Py4JJavaError: An error occurred while calling o1
someone can help me about this issues
py4j.protocol.Py4JJavaError: An error occurred while calling o126.parquet.
: org.apache.spark.SparkException: Job aborted.
at
org.apache.spark.sql.execution.datasources.InsertIntoHadoopFsRelation$$anonfun$run$1.apply$mcV$sp(InsertIntoHadoopFsRelation
