[jira] [Commented] (SPARK-14423) Handle jar conflict issue when uploading to distributed cache
[ https://issues.apache.org/jira/browse/SPARK-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898256#comment-15898256 ] Junping Du commented on SPARK-14423: Thanks [~jerryshao] for reporting this issue. I think YARN should fix this problem also. If the same jars are added to distributed cache, it should detect and failed fast with throwing indicating messages: YARN-5306 already get filed to track this issue. > Handle jar conflict issue when uploading to distributed cache > - > > Key: SPARK-14423 > URL: https://issues.apache.org/jira/browse/SPARK-14423 > Project: Spark > Issue Type: Bug > Components: YARN >Affects Versions: 2.0.0 >Reporter: Saisai Shao >Assignee: Saisai Shao > Fix For: 2.0.0 > > > Currently with the introduction of assembly-free deployment of Spark, by > default yarn#client will upload all the jars in assembly to HDFS staging > folder. If the jars in assembly and specified with \--jars have the same > name, this will introduce exception while downloading these jars and make the > application fail to run. > Here is the exception when running example with {{run-example}}: > {noformat} > 16/04/06 10:29:48 INFO Client: Application report for > application_1459907402325_0004 (state: FAILED) > 16/04/06 10:29:48 INFO Client: >client token: N/A >diagnostics: Application application_1459907402325_0004 failed 2 times > due to AM Container for appattempt_1459907402325_0004_02 exited with > exitCode: -1000 > For more detailed output, check application tracking > page:http://hw12100.local:8088/proxy/application_1459907402325_0004/Then, > click on links to logs of each attempt. > Diagnostics: Resource > hdfs://localhost:8020/user/sshao/.sparkStaging/application_1459907402325_0004/avro-mapred-1.7.7-hadoop2.jar > changed on src filesystem (expected 1459909780508, was 1459909782590 > java.io.IOException: Resource > hdfs://localhost:8020/user/sshao/.sparkStaging/application_1459907402325_0004/avro-mapred-1.7.7-hadoop2.jar > changed on src filesystem (expected 1459909780508, was 1459909782590 > at org.apache.hadoop.yarn.util.FSDownload.copy(FSDownload.java:253) > at org.apache.hadoop.yarn.util.FSDownload.access$000(FSDownload.java:61) > at org.apache.hadoop.yarn.util.FSDownload$2.run(FSDownload.java:359) > at org.apache.hadoop.yarn.util.FSDownload$2.run(FSDownload.java:357) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628) > at org.apache.hadoop.yarn.util.FSDownload.call(FSDownload.java:356) > at org.apache.hadoop.yarn.util.FSDownload.call(FSDownload.java:60) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > The problem is that this jar {{avro-mapred-1.7.7-hadoop2.jar}} both existed > in assembly and example folder. > We should handle this situation, since now spark example is failed to run > under yarn mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-14423) Handle jar conflict issue when uploading to distributed cache
[ https://issues.apache.org/jira/browse/SPARK-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228062#comment-15228062 ] Apache Spark commented on SPARK-14423: -- User 'jerryshao' has created a pull request for this issue: https://github.com/apache/spark/pull/12203 > Handle jar conflict issue when uploading to distributed cache > - > > Key: SPARK-14423 > URL: https://issues.apache.org/jira/browse/SPARK-14423 > Project: Spark > Issue Type: Bug > Components: YARN >Affects Versions: 2.0.0 >Reporter: Saisai Shao > > Currently with the introduction of assembly-free deployment of Spark, by > default yarn#client will upload all the jars in assembly to HDFS staging > folder. If the jars in assembly and specified with \--jars have the same > name, this will introduce exception while downloading these jars and make the > application fail to run. > Here is the exception when running example with {{run-example}}: > {noformat} > 16/04/06 10:29:48 INFO Client: Application report for > application_1459907402325_0004 (state: FAILED) > 16/04/06 10:29:48 INFO Client: >client token: N/A >diagnostics: Application application_1459907402325_0004 failed 2 times > due to AM Container for appattempt_1459907402325_0004_02 exited with > exitCode: -1000 > For more detailed output, check application tracking > page:http://hw12100.local:8088/proxy/application_1459907402325_0004/Then, > click on links to logs of each attempt. > Diagnostics: Resource > hdfs://localhost:8020/user/sshao/.sparkStaging/application_1459907402325_0004/avro-mapred-1.7.7-hadoop2.jar > changed on src filesystem (expected 1459909780508, was 1459909782590 > java.io.IOException: Resource > hdfs://localhost:8020/user/sshao/.sparkStaging/application_1459907402325_0004/avro-mapred-1.7.7-hadoop2.jar > changed on src filesystem (expected 1459909780508, was 1459909782590 > at org.apache.hadoop.yarn.util.FSDownload.copy(FSDownload.java:253) > at org.apache.hadoop.yarn.util.FSDownload.access$000(FSDownload.java:61) > at org.apache.hadoop.yarn.util.FSDownload$2.run(FSDownload.java:359) > at org.apache.hadoop.yarn.util.FSDownload$2.run(FSDownload.java:357) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628) > at org.apache.hadoop.yarn.util.FSDownload.call(FSDownload.java:356) > at org.apache.hadoop.yarn.util.FSDownload.call(FSDownload.java:60) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > The problem is that this jar {{avro-mapred-1.7.7-hadoop2.jar}} both existed > in assembly and example folder. > We should handle this situation, since now spark example is failed to run > under yarn mode. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-14423) Handle jar conflict issue when uploading to distributed cache
[ https://issues.apache.org/jira/browse/SPARK-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227664#comment-15227664 ] Saisai Shao commented on SPARK-14423: - I will fix it soon. > Handle jar conflict issue when uploading to distributed cache > - > > Key: SPARK-14423 > URL: https://issues.apache.org/jira/browse/SPARK-14423 > Project: Spark > Issue Type: Bug > Components: YARN >Affects Versions: 2.0.0 >Reporter: Saisai Shao > > Currently with the introduction of assembly-free deployment of Spark, by > default yarn#client will upload all the jars in assembly to HDFS staging > folder. If the jars in assembly and specified with \--jars have the same > name, this will introduce exception while downloading these jars and make the > application fail to run. > Here is the exception when running example with {{run-example}}: > {noformat} > 16/04/06 10:29:48 INFO Client: Application report for > application_1459907402325_0004 (state: FAILED) > 16/04/06 10:29:48 INFO Client: >client token: N/A >diagnostics: Application application_1459907402325_0004 failed 2 times > due to AM Container for appattempt_1459907402325_0004_02 exited with > exitCode: -1000 > For more detailed output, check application tracking > page:http://hw12100.local:8088/proxy/application_1459907402325_0004/Then, > click on links to logs of each attempt. > Diagnostics: Resource > hdfs://localhost:8020/user/sshao/.sparkStaging/application_1459907402325_0004/avro-mapred-1.7.7-hadoop2.jar > changed on src filesystem (expected 1459909780508, was 1459909782590 > java.io.IOException: Resource > hdfs://localhost:8020/user/sshao/.sparkStaging/application_1459907402325_0004/avro-mapred-1.7.7-hadoop2.jar > changed on src filesystem (expected 1459909780508, was 1459909782590 > at org.apache.hadoop.yarn.util.FSDownload.copy(FSDownload.java:253) > at org.apache.hadoop.yarn.util.FSDownload.access$000(FSDownload.java:61) > at org.apache.hadoop.yarn.util.FSDownload$2.run(FSDownload.java:359) > at org.apache.hadoop.yarn.util.FSDownload$2.run(FSDownload.java:357) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628) > at org.apache.hadoop.yarn.util.FSDownload.call(FSDownload.java:356) > at org.apache.hadoop.yarn.util.FSDownload.call(FSDownload.java:60) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > The problem is that this jar {{avro-mapred-1.7.7-hadoop2.jar}} both existed > in assembly and example folder. > We should handle this situation, since now spark example is failed to run > under yarn mode. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org