[
https://issues.apache.org/jira/browse/TWILL-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951733#comment-15951733
]
ASF GitHub Bot commented on TWILL-228:
--------------------------------------
GitHub user chtyim opened a pull request:
https://github.com/apache/twill/pull/50
(TWILL-228) Remove the optimization when building application jar
- The optimization can leading skipping certain jars in the application jar
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chtyim/twill feature/TWILL-228
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/twill/pull/50.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #50
----
commit f14000bcee275988170b6d3b0178bfd9a8e2ba9a
Author: Terence Yim <cht...@apache.org>
Date: 2017-03-31T22:39:20Z
(TWILL-228) Remove the optimization when building application jar
- The optimization can leading skipping certain jars in the application jar
----
> Application jar is not properly built when the client bundles application and
> twill classes in the same fat jar
> ---------------------------------------------------------------------------------------------------------------
>
> Key: TWILL-228
> URL: https://issues.apache.org/jira/browse/TWILL-228
> Project: Apache Twill
> Issue Type: Bug
> Components: yarn
> Affects Versions: 0.10.0
> Reporter: Sam William
> Assignee: Terence Yim
> Fix For: 0.11.0
>
>
> The actual error the client sees is
> Application application_1484158548936_11154 failed 2 times due to AM
> Container for appattempt_1484158548936_11154_000002 exited with exitCode:
> -1000
> For more detailed output, check application tracking page<> Then, click on
> links to logs of each attempt.
> Diagnostics: No such file or directory
> ENOENT: No such file or directory
> at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmodImpl(Native Method)
> at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmod(NativeIO.java:230)
> at
> org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:660)
> at
> org.apache.hadoop.fs.DelegateToFileSystem.setPermission(DelegateToFileSystem.java:206)
> at org.apache.hadoop.fs.FilterFs.setPermission(FilterFs.java:251)
> at org.apache.hadoop.fs.FileContext$10.next(FileContext.java:955)
> at org.apache.hadoop.fs.FileContext$10.next(FileContext.java:951)
> at org.apache.hadoop.fs.FSLinkResolver.resolve(FSLinkResolver.java:90)
> at org.apache.hadoop.fs.FileContext.setPermission(FileContext.java:951)
> at org.apache.hadoop.yarn.util.FSDownload$3.run(FSDownload.java:419)
> at org.apache.hadoop.yarn.util.FSDownload$3.run(FSDownload.java:417)
> 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:1693)
> at
> org.apache.hadoop.yarn.util.FSDownload.changePermissions(FSDownload.java:417)
> at org.apache.hadoop.yarn.util.FSDownload.call(FSDownload.java:363)
> 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)
> Failing this attempt. Failing the application.
> Digging in a little bit, it appears this happens when all the application
> classes and twill classes and bundled together in the same fat jar. This
> workaround helped
> https://github.com/sampd/twill/compare/branch-0.10.0...sampd:v10_test?expand=1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
