[jira] [Commented] (TEZ-2756) MergeManager close should not try merging files on close if invoked after a shuffle exception
[ https://issues.apache.org/jira/browse/TEZ-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179517#comment-15179517 ] Tsuyoshi Ozawa commented on TEZ-2756: - [~rajesh.balamohan] thanks Rajesh for the reviewing and committing this. > MergeManager close should not try merging files on close if invoked after a > shuffle exception > - > > Key: TEZ-2756 > URL: https://issues.apache.org/jira/browse/TEZ-2756 > Project: Apache Tez > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Siddharth Seth >Assignee: Tsuyoshi Ozawa > Fix For: 0.8.3 > > Attachments: TEZ-2756.001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2954) Container launch timeouts should count towards node blacklisting
[ https://issues.apache.org/jira/browse/TEZ-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179515#comment-15179515 ] Tsuyoshi Ozawa commented on TEZ-2954: - I think the patch includes TEZ-925. [~sseth] could you take a look? > Container launch timeouts should count towards node blacklisting > > > Key: TEZ-2954 > URL: https://issues.apache.org/jira/browse/TEZ-2954 > Project: Apache Tez > Issue Type: Improvement >Reporter: Siddharth Seth >Assignee: Tsuyoshi Ozawa > Attachments: TEZ-2954.001.patch > > > Currently, only task failures count towards blacklisting. A container timing > out should do the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TEZ-2954) Container launch timeouts should count towards node blacklisting
[ https://issues.apache.org/jira/browse/TEZ-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa reassigned TEZ-2954: --- Assignee: Tsuyoshi Ozawa > Container launch timeouts should count towards node blacklisting > > > Key: TEZ-2954 > URL: https://issues.apache.org/jira/browse/TEZ-2954 > Project: Apache Tez > Issue Type: Improvement >Reporter: Siddharth Seth >Assignee: Tsuyoshi Ozawa > Attachments: TEZ-2954.001.patch > > > Currently, only task failures count towards blacklisting. A container timing > out should do the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2954) Container launch timeouts should count towards node blacklisting
[ https://issues.apache.org/jira/browse/TEZ-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated TEZ-2954: Attachment: TEZ-2954.001.patch Attaching a first patch to consider container-launch timeout towards node blacklisting. > Container launch timeouts should count towards node blacklisting > > > Key: TEZ-2954 > URL: https://issues.apache.org/jira/browse/TEZ-2954 > Project: Apache Tez > Issue Type: Improvement >Reporter: Siddharth Seth > Attachments: TEZ-2954.001.patch > > > Currently, only task failures count towards blacklisting. A container timing > out should do the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: TEZ-3155 PreCommit Build #1541
Jira: https://issues.apache.org/jira/browse/TEZ-3155
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1541/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 4618 lines...]
[INFO] Build failures were ignored.
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12791361/TEZ-3155.1.patch
against master revision 2af886b.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 33 javac
compiler warnings (more than the master's current 31 warnings).
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 2 new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.tez.test.TestRecovery
org.apache.tez.test.TestTezJobs
org.apache.tez.test.TestFaultTolerance
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1541//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1541//artifact/patchprocess/newPatchFindbugsWarningstez-dag.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1541//artifact/patchprocess/newPatchFindbugsWarningstez-api.html
Javac warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1541//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1541//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
dda0b5a2a5857f06da8be912eb409078c16ca7cc logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
21 tests failed.
FAILED: org.apache.tez.test.TestFaultTolerance.testRandomFailingInputs
Error Message:
expected: but was:
Stack Trace:
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:141)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:124)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:120)
at
org.apache.tez.test.TestFaultTolerance.testRandomFailingInputs(TestFaultTolerance.java:763)
FAILED: org.apache.tez.test.TestFaultTolerance.testBasicInputFailureWithExit
Error Message:
TezSession has already shutdown. No cluster diagnostics found.
Stack Trace:
org.apache.tez.dag.api.SessionNotRunning: TezSession has already shutdown. No
cluster diagnostics found.
at org.apache.tez.client.TezClient.waitTillReady(TezClient.java:814)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:129)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:124)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:120)
at
org.apache.tez.test.TestFaultTolerance.testBasicInputFailureWithExit(TestFaultTolerance.java:261)
FAILED:
org.apache.tez.test.TestFaultTolerance.testInputFailureRerunCanSendOutputToTwoDownstreamVertices
Error Message:
TezSession has already shutdown. No cluster diagnostics found.
Stack Trace:
org.apache.tez.dag.api.SessionNotRunning: TezSession has already shutdown. No
cluster diagnostics found.
at org.apache
[jira] [Commented] (TEZ-3155) Support a way to submit DAGs to a session where the DAG plan exceeds hadoop ipc limits
[
https://issues.apache.org/jira/browse/TEZ-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179114#comment-15179114
]
TezQA commented on TEZ-3155:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12791361/TEZ-3155.1.patch
against master revision 2af886b.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 33 javac
compiler warnings (more than the master's current 31 warnings).
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 2 new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.tez.test.TestRecovery
org.apache.tez.test.TestTezJobs
org.apache.tez.test.TestFaultTolerance
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1541//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1541//artifact/patchprocess/newPatchFindbugsWarningstez-dag.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1541//artifact/patchprocess/newPatchFindbugsWarningstez-api.html
Javac warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1541//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1541//console
This message is automatically generated.
> Support a way to submit DAGs to a session where the DAG plan exceeds hadoop
> ipc limits
> ---
>
> Key: TEZ-3155
> URL: https://issues.apache.org/jira/browse/TEZ-3155
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Hitesh Shah
>Assignee: Zhiyuan Yang
> Attachments: TEZ-3155.1.patch
>
>
> Currently, dag submissions fail if the dag plan exceeds the hadoop ipc
> limits. One option would be to fall back to local resources if the dag plan
> is too large.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEZ-2756) MergeManager close should not try merging files on close if invoked after a shuffle exception
[ https://issues.apache.org/jira/browse/TEZ-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179111#comment-15179111 ] Rajesh Balamohan commented on TEZ-2756: --- lgtm. +1 Can you please remove TezRawKeyValueIterator import in TestMergeManager before committing? Thanks. > MergeManager close should not try merging files on close if invoked after a > shuffle exception > - > > Key: TEZ-2756 > URL: https://issues.apache.org/jira/browse/TEZ-2756 > Project: Apache Tez > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Siddharth Seth >Assignee: Tsuyoshi Ozawa > Attachments: TEZ-2756.001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2756) MergeManager close should not try merging files on close if invoked after a shuffle exception
[ https://issues.apache.org/jira/browse/TEZ-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179076#comment-15179076 ] Hitesh Shah commented on TEZ-2756: -- \cc [~rajesh.balamohan] > MergeManager close should not try merging files on close if invoked after a > shuffle exception > - > > Key: TEZ-2756 > URL: https://issues.apache.org/jira/browse/TEZ-2756 > Project: Apache Tez > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Siddharth Seth >Assignee: Tsuyoshi Ozawa > Attachments: TEZ-2756.001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2756) MergeManager close should not try merging files on close if invoked after a shuffle exception
[ https://issues.apache.org/jira/browse/TEZ-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179041#comment-15179041 ] Tsuyoshi Ozawa commented on TEZ-2756: - [~sseth] could you take a look? > MergeManager close should not try merging files on close if invoked after a > shuffle exception > - > > Key: TEZ-2756 > URL: https://issues.apache.org/jira/browse/TEZ-2756 > Project: Apache Tez > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Siddharth Seth >Assignee: Tsuyoshi Ozawa > Attachments: TEZ-2756.001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2580) Remove VertexManagerPlugin#setVertexParallelism with VertexManagerPlugin#reconfigureVertex
[ https://issues.apache.org/jira/browse/TEZ-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179039#comment-15179039 ] Tsuyoshi Ozawa commented on TEZ-2580: - Make sense. Pending this for that it's done. > Remove VertexManagerPlugin#setVertexParallelism with > VertexManagerPlugin#reconfigureVertex > -- > > Key: TEZ-2580 > URL: https://issues.apache.org/jira/browse/TEZ-2580 > Project: Apache Tez > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Tsuyoshi Ozawa >Priority: Blocker > Attachments: TEZ-2580.001.patch > > > This was deprecated in 0.7. Should be replaced with reconfigureVertex() - > change of name - to make it consistent with other reconfigureVertex() API's. > Should be done just close to release to enabled Hive to continue to build/use > master of Tez. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3155) Support a way to submit DAGs to a session where the DAG plan exceeds hadoop ipc limits
[ https://issues.apache.org/jira/browse/TEZ-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated TEZ-3155: -- Attachment: TEZ-3155.1.patch > Support a way to submit DAGs to a session where the DAG plan exceeds hadoop > ipc limits > --- > > Key: TEZ-3155 > URL: https://issues.apache.org/jira/browse/TEZ-3155 > Project: Apache Tez > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Zhiyuan Yang > Attachments: TEZ-3155.1.patch > > > Currently, dag submissions fail if the dag plan exceeds the hadoop ipc > limits. One option would be to fall back to local resources if the dag plan > is too large. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3156) Tez client keep trying to talk to RM even if RM does not know about the application
[
https://issues.apache.org/jira/browse/TEZ-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated TEZ-3156:
-
Summary: Tez client keep trying to talk to RM even if RM does not know
about the application (was: Tez client keep trying to talk to RM if RM does
not know application)
> Tez client keep trying to talk to RM even if RM does not know about the
> application
> ---
>
> Key: TEZ-3156
> URL: https://issues.apache.org/jira/browse/TEZ-3156
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Hitesh Shah
> Attachments: TEZ-3156.1.patch, TEZ-3156.2.patch
>
>
> Scenario :
> * Set RM/NM recovery to false.
> {code}
>
> yarn.resourcemanager.recovery.enabled
> false
>
>
> yarn.nodemanager.recovery.enabled
> false
>
> {code}
> * Start Mrrsleep application (application_1456883132071_0001)
> {code}
> hadoop jar tez-tests-*.jar mrrsleep -m 1 -r 1 -mt 100 -rt 1000
> {code}
> * When application is running, restart RM
> Since recovery is disabled and RM is restarted, it forgets mrrsleep
> application. At this point, mrrsleep application's tez-client keep trying to
> communicate with RM and loads RM with below exception.
> {code}
> 2016-03-02 02:01:24,708 INFO ipc.Server (Server.java:run(2172)) - IPC Server
> handler 18 on 8050, call
> org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplicationReport
> from xx.xx.xx.xxx:36191 Call#500250 Retry#0
> org.apache.hadoop.yarn.exceptions.ApplicationNotFoundException: Application
> with id 'application_1456883132071_0001' doesn't exist in RM.
> at
> org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.getApplicationReport(ClientRMService.java:328)
> at
> org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.getApplicationReport(ApplicationClientProtocolPBServiceImpl.java:175)
> at
> org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:417)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2151)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2147)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2145)
> 2016-03-02 02:01:24,709 INFO ipc.Server (Server.java:run(2172)) - IPC Server
> handler 27 on 8050, call
> org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplicationReport
> from xx.xx.xx.xxx:36191 Call#500251 Retry#0
> org.apache.hadoop.yarn.exceptions.ApplicationNotFoundException: Application
> with id 'application_1456883132071_0001' doesn't exist in RM.
> at
> org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.getApplicationReport(ClientRMService.java:328)
> at
> org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.getApplicationReport(ApplicationClientProtocolPBServiceImpl.java:175)
> at
> org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:417)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2151)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2147)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2145)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TEZ-3156) Tez client keeps trying to talk to RM even if RM does not know about the application
[
https://issues.apache.org/jira/browse/TEZ-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated TEZ-3156:
-
Summary: Tez client keeps trying to talk to RM even if RM does not know
about the application (was: Tez client keep trying to talk to RM even if RM
does not know about the application)
> Tez client keeps trying to talk to RM even if RM does not know about the
> application
>
>
> Key: TEZ-3156
> URL: https://issues.apache.org/jira/browse/TEZ-3156
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Hitesh Shah
> Attachments: TEZ-3156.1.patch, TEZ-3156.2.patch
>
>
> Scenario :
> * Set RM/NM recovery to false.
> {code}
>
> yarn.resourcemanager.recovery.enabled
> false
>
>
> yarn.nodemanager.recovery.enabled
> false
>
> {code}
> * Start Mrrsleep application (application_1456883132071_0001)
> {code}
> hadoop jar tez-tests-*.jar mrrsleep -m 1 -r 1 -mt 100 -rt 1000
> {code}
> * When application is running, restart RM
> Since recovery is disabled and RM is restarted, it forgets mrrsleep
> application. At this point, mrrsleep application's tez-client keep trying to
> communicate with RM and loads RM with below exception.
> {code}
> 2016-03-02 02:01:24,708 INFO ipc.Server (Server.java:run(2172)) - IPC Server
> handler 18 on 8050, call
> org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplicationReport
> from xx.xx.xx.xxx:36191 Call#500250 Retry#0
> org.apache.hadoop.yarn.exceptions.ApplicationNotFoundException: Application
> with id 'application_1456883132071_0001' doesn't exist in RM.
> at
> org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.getApplicationReport(ClientRMService.java:328)
> at
> org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.getApplicationReport(ApplicationClientProtocolPBServiceImpl.java:175)
> at
> org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:417)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2151)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2147)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2145)
> 2016-03-02 02:01:24,709 INFO ipc.Server (Server.java:run(2172)) - IPC Server
> handler 27 on 8050, call
> org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplicationReport
> from xx.xx.xx.xxx:36191 Call#500251 Retry#0
> org.apache.hadoop.yarn.exceptions.ApplicationNotFoundException: Application
> with id 'application_1456883132071_0001' doesn't exist in RM.
> at
> org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.getApplicationReport(ClientRMService.java:328)
> at
> org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.getApplicationReport(ApplicationClientProtocolPBServiceImpl.java:175)
> at
> org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:417)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2151)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2147)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2145)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEZ-3152) Tez UI 2: Build fails when run by multiple users or when node_modules is old
[
https://issues.apache.org/jira/browse/TEZ-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178472#comment-15178472
]
TezQA commented on TEZ-3152:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12791236/err2
against master revision 3f5a7f3.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1540//console
This message is automatically generated.
> Tez UI 2: Build fails when run by multiple users or when node_modules is old
>
>
> Key: TEZ-3152
> URL: https://issues.apache.org/jira/browse/TEZ-3152
> Project: Apache Tez
> Issue Type: Sub-task
>Reporter: Sreenath Somarajapuram
>Assignee: Sreenath Somarajapuram
> Attachments: TEZ-3152.1.patch, TEZ-3152.wip.1.patch, err2
>
>
> We have two separate cases in which the build fails:
> #1 The build uses Nodejs v0.12.2. When the webapp folder already have a
> node_modules folder installed by an old version of node, build fails.
> - To repro, just manually run npm install in webapp with an old node (Like
> v0.10.36). Then run mvn package from tez.
> #2 async-disk-cache package creates files in tmpDir (/tmp). When run from a
> different user, because of user permission on there files, the build fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: TEZ-3152 PreCommit Build #1540
Jira: https://issues.apache.org/jira/browse/TEZ-3152
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1540/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 27 lines...]
Testing patch for TEZ-3152.
==
==
HEAD is now at 3f5a7f3 TEZ-3115. Shuffle string handling adds significant
memory overhead (jeagles)
Previous HEAD position was 3f5a7f3... TEZ-3115. Shuffle string handling adds
significant memory overhead (jeagles)
Switched to branch 'master'
Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.
(use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded master to 3f5a7f35dd5a8e28fcf56c2e2bdad86f8d7febbf.
TEZ-3152 patch is being downloaded at Thu Mar 3 19:41:42 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12791236/err2
patch: Only garbage was found in the patch input.
patch: Only garbage was found in the patch input.
patch: Only garbage was found in the patch input.
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12791236/err2
against master revision 3f5a7f3.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1540//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
e7b1571b8f219d2f59e519ff9209182dd7ed8490 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
No tests ran.
[jira] [Updated] (TEZ-3152) Tez UI 2: Build fails when run by multiple users or when node_modules is old
[ https://issues.apache.org/jira/browse/TEZ-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated TEZ-3152: Attachment: err2 Still failing. Attached output of mvn clean install -X from the tez-ui2 directory > Tez UI 2: Build fails when run by multiple users or when node_modules is old > > > Key: TEZ-3152 > URL: https://issues.apache.org/jira/browse/TEZ-3152 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3152.1.patch, TEZ-3152.wip.1.patch, err2 > > > We have two separate cases in which the build fails: > #1 The build uses Nodejs v0.12.2. When the webapp folder already have a > node_modules folder installed by an old version of node, build fails. > - To repro, just manually run npm install in webapp with an old node (Like > v0.10.36). Then run mvn package from tez. > #2 async-disk-cache package creates files in tmpDir (/tmp). When run from a > different user, because of user permission on there files, the build fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3156) Tez client keep trying to talk to RM if RM does not know application
[
https://issues.apache.org/jira/browse/TEZ-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178372#comment-15178372
]
Siddharth Seth commented on TEZ-3156:
-
+1.
> Tez client keep trying to talk to RM if RM does not know application
>
>
> Key: TEZ-3156
> URL: https://issues.apache.org/jira/browse/TEZ-3156
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Hitesh Shah
> Attachments: TEZ-3156.1.patch, TEZ-3156.2.patch
>
>
> Scenario :
> * Set RM/NM recovery to false.
> {code}
>
> yarn.resourcemanager.recovery.enabled
> false
>
>
> yarn.nodemanager.recovery.enabled
> false
>
> {code}
> * Start Mrrsleep application (application_1456883132071_0001)
> {code}
> hadoop jar tez-tests-*.jar mrrsleep -m 1 -r 1 -mt 100 -rt 1000
> {code}
> * When application is running, restart RM
> Since recovery is disabled and RM is restarted, it forgets mrrsleep
> application. At this point, mrrsleep application's tez-client keep trying to
> communicate with RM and loads RM with below exception.
> {code}
> 2016-03-02 02:01:24,708 INFO ipc.Server (Server.java:run(2172)) - IPC Server
> handler 18 on 8050, call
> org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplicationReport
> from xx.xx.xx.xxx:36191 Call#500250 Retry#0
> org.apache.hadoop.yarn.exceptions.ApplicationNotFoundException: Application
> with id 'application_1456883132071_0001' doesn't exist in RM.
> at
> org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.getApplicationReport(ClientRMService.java:328)
> at
> org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.getApplicationReport(ApplicationClientProtocolPBServiceImpl.java:175)
> at
> org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:417)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2151)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2147)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2145)
> 2016-03-02 02:01:24,709 INFO ipc.Server (Server.java:run(2172)) - IPC Server
> handler 27 on 8050, call
> org.apache.hadoop.yarn.api.ApplicationClientProtocolPB.getApplicationReport
> from xx.xx.xx.xxx:36191 Call#500251 Retry#0
> org.apache.hadoop.yarn.exceptions.ApplicationNotFoundException: Application
> with id 'application_1456883132071_0001' doesn't exist in RM.
> at
> org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.getApplicationReport(ClientRMService.java:328)
> at
> org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.getApplicationReport(ApplicationClientProtocolPBServiceImpl.java:175)
> at
> org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:417)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2151)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2147)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2145)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TEZ-3087) Tez UI 2: Log links must be added in task & attempt details page
[ https://issues.apache.org/jira/browse/TEZ-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3087: Summary: Tez UI 2: Log links must be added in task & attempt details page (was: Tez UI 2: Log links must added in task & attempt details page) > Tez UI 2: Log links must be added in task & attempt details page > > > Key: TEZ-3087 > URL: https://issues.apache.org/jira/browse/TEZ-3087 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram > > - UI1 implementation takes you to the container logs and doesn't works as > expected > - Ensure that the functionality is inline with TEZ-3101 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3152) Tez UI 2: Build fails when run by multiple users or when node_modules is old
[
https://issues.apache.org/jira/browse/TEZ-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177955#comment-15177955
]
Hitesh Shah commented on TEZ-3152:
--
I see the following:
{code}
[INFO] --- frontend-maven-plugin:0.0.23:install-node-and-npm (install node and
npm) @ tez-ui2 ---
[INFO] Node v0.12.2 is already installed.
[INFO] --- exec-maven-plugin:1.3.2:exec (ember build) @ tez-ui2 ---
> tez-ui@0.2.0 build /Users/hitesh/dev/apache/tez/tez-ui2/src/main/webapp
> TMPDIR=tmp ember build -prod
DEPRECATION: Node v0.10.29 is no longer supported by Ember CLI. Please update
to a more recent version of Node
undefined
version: 1.13.13
{code}
Is the build using the incorrect npm i.e. instead of using npm that was
installed by frontend-maven-plugin, it is using the npm that is available
somewhere in the system env?
> Tez UI 2: Build fails when run by multiple users or when node_modules is old
>
>
> Key: TEZ-3152
> URL: https://issues.apache.org/jira/browse/TEZ-3152
> Project: Apache Tez
> Issue Type: Sub-task
>Reporter: Sreenath Somarajapuram
>Assignee: Sreenath Somarajapuram
> Attachments: TEZ-3152.1.patch, TEZ-3152.wip.1.patch
>
>
> We have two separate cases in which the build fails:
> #1 The build uses Nodejs v0.12.2. When the webapp folder already have a
> node_modules folder installed by an old version of node, build fails.
> - To repro, just manually run npm install in webapp with an old node (Like
> v0.10.36). Then run mvn package from tez.
> #2 async-disk-cache package creates files in tmpDir (/tmp). When run from a
> different user, because of user permission on there files, the build fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (TEZ-3087) Tez UI 2: Log links must added in task & attempt details page
[ https://issues.apache.org/jira/browse/TEZ-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177931#comment-15177931 ] Hitesh Shah edited comment on TEZ-3087 at 3/3/16 3:15 PM: -- What do you mean by task attempt redirection? Is this for fixing a bug in Tez or in Yarn? There are links already to logs for the task attempts - what are we missing that needs to be added in the Tez UI? was (Author: hitesh): What do you mean by task attempt redirection? Is this for fixing a bug in Tez or in Yarn? > Tez UI 2: Log links must added in task & attempt details page > - > > Key: TEZ-3087 > URL: https://issues.apache.org/jira/browse/TEZ-3087 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram > > - UI1 implementation takes you to the container logs and doesn't works as > expected > - Ensure that the functionality is inline with TEZ-3101 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3087) Tez UI 2: Log links must added in task & attempt details page
[ https://issues.apache.org/jira/browse/TEZ-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177931#comment-15177931 ] Hitesh Shah commented on TEZ-3087: -- What do you mean by task attempt redirection? Is this for fixing a bug in Tez or in Yarn? > Tez UI 2: Log links must added in task & attempt details page > - > > Key: TEZ-3087 > URL: https://issues.apache.org/jira/browse/TEZ-3087 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram > > - UI1 implementation takes you to the container logs and doesn't works as > expected > - Ensure that the functionality is inline with TEZ-3101 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3152) Tez UI 2: Build fails when run by multiple users or when node_modules is old
[
https://issues.apache.org/jira/browse/TEZ-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177805#comment-15177805
]
TezQA commented on TEZ-3152:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12791159/TEZ-3152.1.patch
against master revision 3f5a7f3.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.tez.mapreduce.TestMRRJobsDAGApi
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1539//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1539//console
This message is automatically generated.
> Tez UI 2: Build fails when run by multiple users or when node_modules is old
>
>
> Key: TEZ-3152
> URL: https://issues.apache.org/jira/browse/TEZ-3152
> Project: Apache Tez
> Issue Type: Sub-task
>Reporter: Sreenath Somarajapuram
>Assignee: Sreenath Somarajapuram
> Attachments: TEZ-3152.1.patch, TEZ-3152.wip.1.patch
>
>
> We have two separate cases in which the build fails:
> #1 The build uses Nodejs v0.12.2. When the webapp folder already have a
> node_modules folder installed by an old version of node, build fails.
> - To repro, just manually run npm install in webapp with an old node (Like
> v0.10.36). Then run mvn package from tez.
> #2 async-disk-cache package creates files in tmpDir (/tmp). When run from a
> different user, because of user permission on there files, the build fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: TEZ-3152 PreCommit Build #1539
Jira: https://issues.apache.org/jira/browse/TEZ-3152
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1539/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 4411 lines...]
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :tez-tests
[INFO] Build failures were ignored.
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12791159/TEZ-3152.1.patch
against master revision 3f5a7f3.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.tez.mapreduce.TestMRRJobsDAGApi
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1539//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1539//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
b392773555bd0416ba9647029f73911af2160522 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
6 tests failed.
FAILED:
org.apache.tez.mapreduce.TestMRRJobsDAGApi.testMultipleMRRSleepJobViaSession
Error Message:
expected: but was:
Stack Trace:
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.tez.mapreduce.TestMRRJobsDAGApi.testMultipleMRRSleepJobViaSession(TestMRRJobsDAGApi.java:500)
FAILED: org.apache.tez.mapreduce.TestMRRJobsDAGApi.testNonDefaultFSStagingDir
Error Message:
test timed out after 6 milliseconds
Stack Trace:
java.lang.Exception: test timed out after 6 milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.tez.client.TezClient.waitNonSessionTillReady(TezClient.java:804)
at
org.apache.tez.client.TezClient.submitDAGApplication(TezClient.java:900)
at
org.apache.tez.client.TezClient.submitDAGApplication(TezClient.java:855)
at org.apache.tez.client.TezClient.submitDAG(TezClient.java:454)
at
org.apache.tez.mapreduce.TestMRRJobsDAGApi.testNonDefaultFSStagingDir(TestMRRJobsDAGApi.java:244)
FAILED: org.apache.tez.mapreduce.TestMRRJobsDAGApi.testMRRSleepJobDagSubmit
Error Message:
test timed out after 6 milliseconds
Stack Trace:
java.lang.Exception: test timed out after 6 milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.tez.client.TezClient.waitNonSessionTillReady(TezClient.java:804)
at
org.apache.tez.client.TezClient.submitDAGApplication(TezClient.java:900)
at
org.apache.tez.client.TezClient.submitDAGApplication(TezClient.java:855)
at org.apache.tez.client.TezClient.submitDAG(TezClient.java:454)
at
org.apache.tez.mapreduce.TestMRRJobsDAGApi.testMRRSleepJobDagSubmitCore(TestMRRJobsDAGApi.java:699)
at
org.apache.tez.mapreduce.TestMRRJobsDAGApi.testMRRSleepJobDagSubmitCore(TestMRRJobsDAGApi.java:542)
at
org.apache.tez.
[jira] [Updated] (TEZ-3152) Tez UI 2: Build fails when run by multiple users or when node_modules is old
[ https://issues.apache.org/jira/browse/TEZ-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3152: Description: We have two separate cases in which the build fails: # The build uses Nodejs v0.12.2. When the webapp folder already have a node_modules folder installed by an old version of node, build fails. - To repro, just manually run npm install in webapp with an old node (Like v0.10.36). Then run mvn package from tez. # async-disk-cache package creates files in tmpDir (/tmp). When run from a different user, because of user permission on there files, the build fails. was: We have two separate cases in which the build fails: # The build uses Nodejs v0.12.2. When the webapp folder already have a node_modules folder installed by an old version of node, build fails. To repro, just manually run npm install in webapp with an old node (Like v0.10.36). Then run mvn package from tez. # async-disk-cache package creates files in tmpDir (/tmp). When run from a different user, because of user permission on there files, the build fails. > Tez UI 2: Build fails when run by multiple users or when node_modules is old > > > Key: TEZ-3152 > URL: https://issues.apache.org/jira/browse/TEZ-3152 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3152.1.patch, TEZ-3152.wip.1.patch > > > We have two separate cases in which the build fails: > # The build uses Nodejs v0.12.2. When the webapp folder already have a > node_modules folder installed by an old version of node, build fails. > - To repro, just manually run npm install in webapp with an old node (Like > v0.10.36). Then run mvn package from tez. > # async-disk-cache package creates files in tmpDir (/tmp). When run from a > different user, because of user permission on there files, the build fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3152) Tez UI 2: Build fails when run by multiple users or when node_modules is old
[ https://issues.apache.org/jira/browse/TEZ-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3152: Description: We have two separate cases in which the build fails: #1 The build uses Nodejs v0.12.2. When the webapp folder already have a node_modules folder installed by an old version of node, build fails. - To repro, just manually run npm install in webapp with an old node (Like v0.10.36). Then run mvn package from tez. #2 async-disk-cache package creates files in tmpDir (/tmp). When run from a different user, because of user permission on there files, the build fails. was: We have two separate cases in which the build fails: # The build uses Nodejs v0.12.2. When the webapp folder already have a node_modules folder installed by an old version of node, build fails. - To repro, just manually run npm install in webapp with an old node (Like v0.10.36). Then run mvn package from tez. # async-disk-cache package creates files in tmpDir (/tmp). When run from a different user, because of user permission on there files, the build fails. > Tez UI 2: Build fails when run by multiple users or when node_modules is old > > > Key: TEZ-3152 > URL: https://issues.apache.org/jira/browse/TEZ-3152 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3152.1.patch, TEZ-3152.wip.1.patch > > > We have two separate cases in which the build fails: > #1 The build uses Nodejs v0.12.2. When the webapp folder already have a > node_modules folder installed by an old version of node, build fails. > - To repro, just manually run npm install in webapp with an old node (Like > v0.10.36). Then run mvn package from tez. > #2 async-disk-cache package creates files in tmpDir (/tmp). When run from a > different user, because of user permission on there files, the build fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TEZ-3152) Tez UI 2: Build fails when run by multiple users or when node_modules is old
[ https://issues.apache.org/jira/browse/TEZ-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177718#comment-15177718 ] Sreenath Somarajapuram edited comment on TEZ-3152 at 3/3/16 11:57 AM: -- Attaching a clean fix for both the issues. #1 One of the dependent package (ember-cli-font-awesome), had a binding with the node version in use. The same was replaced with build script changes. #2 async-disk-cache issue was fixed by forcing the build to use a local ./tmp directory (that we already use) instead of the global /tmp directory. [~hitesh] please review. was (Author: sreenath): Attaching fix for both the issues. #1 One of the dependent package (ember-cli-font-awesome), had a binding with the node version in use. The same was replaced with build script changes. #2 async-disk-cache issue was fixed by forcing the build to use a local ./tmp directory (that we already use) instead of the global /tmp directory. [~hitesh] please review. > Tez UI 2: Build fails when run by multiple users or when node_modules is old > > > Key: TEZ-3152 > URL: https://issues.apache.org/jira/browse/TEZ-3152 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3152.1.patch, TEZ-3152.wip.1.patch > > > We have two separate cases in which the build fails: > #1 The build uses Nodejs v0.12.2. When the webapp folder already have a > node_modules folder installed by an old version of node, build fails. > - To repro, just manually run npm install in webapp with an old node (Like > v0.10.36). Then run mvn package from tez. > #2 async-disk-cache package creates files in tmpDir (/tmp). When run from a > different user, because of user permission on there files, the build fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3152) Tez UI 2: Build fails when run by multiple users or when node_modules is old
[ https://issues.apache.org/jira/browse/TEZ-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3152: Description: We have two separate cases in which the build fails: # The build uses Nodejs v0.12.2. When the webapp folder already have a node_modules folder installed by an old version of node, build fails. To repro, just manually run npm install in webapp with an old node (Like v0.10.36). Then run mvn package from tez. # async-disk-cache package creates files in tmpDir (/tmp). When run from a different user, because of user permission on there files, the build fails. was: We have two separate cases in which the build fails: # The build uses Nodejs v0.12.2. When the webapp folder already have a node_modules folder installed by an old version of node, build fails. # async-disk-cache package creates files in tmpDir (/tmp). When run from a different user, because of user permission on there files, the build fails. > Tez UI 2: Build fails when run by multiple users or when node_modules is old > > > Key: TEZ-3152 > URL: https://issues.apache.org/jira/browse/TEZ-3152 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3152.1.patch, TEZ-3152.wip.1.patch > > > We have two separate cases in which the build fails: > # The build uses Nodejs v0.12.2. When the webapp folder already have a > node_modules folder installed by an old version of node, build fails. > To repro, just manually run npm install in webapp with an old node (Like > v0.10.36). Then run mvn package from tez. > # async-disk-cache package creates files in tmpDir (/tmp). When run from a > different user, because of user permission on there files, the build fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3152) Tez UI 2: Build fails when run by multiple users or when node_modules is old
[ https://issues.apache.org/jira/browse/TEZ-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3152: Attachment: TEZ-3152.1.patch Attaching fix for both the issues. #1 One of the dependent package (ember-cli-font-awesome), had a binding with the node version in use. The same was replaced with build script changes. #2 async-disk-cache issue was fixed by forcing the build to use a local ./tmp directory (that we already use) instead of the global /tmp directory. [~hitesh] please review. > Tez UI 2: Build fails when run by multiple users or when node_modules is old > > > Key: TEZ-3152 > URL: https://issues.apache.org/jira/browse/TEZ-3152 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3152.1.patch, TEZ-3152.wip.1.patch > > > We have two separate cases in which the build fails: > # The build uses Nodejs v0.12.2. When the webapp folder already have a > node_modules folder installed by an old version of node, build fails. > # async-disk-cache package creates files in tmpDir (/tmp). When run from a > different user, because of user permission on there files, the build fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
