[jira] [Updated] (TEZ-1526) LoadingCache for TezTaskID slow for large jobs
[ https://issues.apache.org/jira/browse/TEZ-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated TEZ-1526: - Attachment: TEZ-1526.5.patch > LoadingCache for TezTaskID slow for large jobs > -- > > Key: TEZ-1526 > URL: https://issues.apache.org/jira/browse/TEZ-1526 > Project: Apache Tez > Issue Type: Improvement >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Labels: performance > Attachments: 10-TezTaskIDs.patch, TEZ-1526-v1.patch, > TEZ-1526-v2.patch, TEZ-1526.3.patch, TEZ-1526.4.patch, TEZ-1526.5.patch > > > Using the LoadingCache with default builder settings. 100,000 TezTaskIDs are > created in 10 seconds on my setup. With a LoadingCache initialCapacity of > 10,000 they are created in 300 ms. With no LoadingCache, they are created in > 10 ms. A test case in attached to illustrate the condition I would like to be > sped up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3206) Have unordered partitioned KV output send partition stats via VertexManagerEvent
[
https://issues.apache.org/jira/browse/TEZ-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15242242#comment-15242242
]
Ming Ma commented on TEZ-3206:
--
Thanks [~jeagles]! AFAIK, partition statistics is via VertexManagerEvent which
stops at AM, while empty partition list is via DataMovementEvent and routed to
AM then reducers. So the size of partition statistics shouldn't impact any
reducer.
For the DataMovementEvent task OOM case, is it because each reducer gets
launched after all 100k mappers have finished and thus fills up its event
queue? I assume the same thing could happen to AM, e.g., VertexManagerEvent
explode AM's event queue. Although that is less likely, as it requires all 100k
mappers finish at the same time or at faster rate than AM async dispatcher can
process.
> Have unordered partitioned KV output send partition stats via
> VertexManagerEvent
> -
>
> Key: TEZ-3206
> URL: https://issues.apache.org/jira/browse/TEZ-3206
> Project: Apache Tez
> Issue Type: New Feature
>Reporter: Ming Ma
>
> As part of the auto-parallelism feature, ordered partitioned KV output's
> partition stats are sent to ShuffleVertexManager via VertexManagerEvent. But
> this isn't available for unordered partitioned output. Having
> {{UnorderedPartitionedKVWriter}} send partition stats will enable the
> auto-parallelism support for unordered KV or other custom data routing
> mechanisms that depend on partition size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TEZ-704) Tez MapReduce job hangs if setting mapreduce.reduce.cpu.vcores to be 2
[ https://issues.apache.org/jira/browse/TEZ-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated TEZ-704: Assignee: (was: Hitesh Shah) > Tez MapReduce job hangs if setting mapreduce.reduce.cpu.vcores to be 2 > -- > > Key: TEZ-704 > URL: https://issues.apache.org/jira/browse/TEZ-704 > Project: Apache Tez > Issue Type: Bug >Reporter: Zhenxiao Luo > > When running Hive on Tez in EMR hadoop districution, which set > mapreduce.reduce.cpu.vcores to be 2 in mapred-site.xml, all MapReduce jobs > get hang, without any progress. > The problem seems like, > Hive On Tez sets mapreduce.reduce.cpu.vcores to 2, so its application > manager asks for a 2 cpu container, but the resource manager could not > allocate a node for it, since all it has are 1 cpu containers. > I saw the same problem when running MapReduce Job on Tez when setting > mapreduce.reduce.cpu.vcores to be 2. > This could be a bug in Tez MapReduce code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: TEZ-3165 PreCommit Build #1656
Jira: https://issues.apache.org/jira/browse/TEZ-3165
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1656/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by remote host 127.0.0.1
[EnvInject] - Loading node environment variables.
Building remotely on H6 (Mapreduce Falcon Hadoop Pig Zookeeper Tez Hdfs
yahoo-not-h2) in workspace
/home/jenkins/jenkins-slave/workspace/PreCommit-TEZ-Build
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://git-wip-us.apache.org/repos/asf/tez.git
> # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/tez.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress
> https://git-wip-us.apache.org/repos/asf/tez.git
> +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 4675a651f874c223cb5968ec39704bc9ba973507
(refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 4675a651f874c223cb5968ec39704bc9ba973507
> git rev-list 53981d4d277f0a1cd9a8a4aa04a1a6ea01dce6cf # timeout=10
No emails were triggered.
[PreCommit-TEZ-Build] $ /bin/bash /tmp/hudson4723528699727275016.sh
Running in Jenkins mode
==
==
Testing patch for TEZ-3165.
==
==
HEAD is now at 4675a65 TEZ-3165. Allow Inputs/Outputs to be initialized
serially, control processor initialization relative to Inputs/Outputs (jeagles)
Previous HEAD position was 4675a65... TEZ-3165. Allow Inputs/Outputs to be
initialized serially, control processor initialization relative to
Inputs/Outputs (jeagles)
Switched to branch 'master'
Your branch is behind 'origin/master' by 7 commits, 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 4675a651f874c223cb5968ec39704bc9ba973507.
TEZ-3165 is not "Patch Available". Exiting.
==
==
Finished build.
==
==
Archiving artifacts
ERROR: No artifacts found that match the file pattern "patchprocess/*.*".
Configuration error?
ERROR: ‘patchprocess/*.*’ doesn’t match anything, but ‘*.*’ does. Perhaps
that’s what you mean?
Build step 'Archive the artifacts' changed build result to FAILURE
[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-3165) Allow Inputs/Outputs to be initialized serially, control processor initialization relative to Inputs/Outputs
[
https://issues.apache.org/jira/browse/TEZ-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Eagles updated TEZ-3165:
-
Attachment: TEZ-3165.4-branch-0.7.patch
> Allow Inputs/Outputs to be initialized serially, control processor
> initialization relative to Inputs/Outputs
>
>
> Key: TEZ-3165
> URL: https://issues.apache.org/jira/browse/TEZ-3165
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Jonathan Eagles
>Assignee: Jonathan Eagles
> Attachments: TEZ-3165.1.patch, TEZ-3165.2.patch, TEZ-3165.3.patch,
> TEZ-3165.4-branch-0.7.patch, TEZ-3165.4.patch
>
>
> 2016-03-13 23:55:17,162 [INFO] [main]
> |runtime.LogicalIOProcessorRuntimeTask|: Initializing
> LogicalIOProcessorRuntimeTask with TaskSpec: DAGName :
> PigLatin:Script.pig-0_scope-0, VertexName: scope-203, VertexParallelism:
> 2707, TaskAttemptID:attempt_1,
> processorName=org.apache.pig.backend.hadoop.executionengine.tez.runtime.PigProcessor,
> inputSpecListSize=1, outputSpecListSize=1, inputSpecList=[{{
> sourceVertexName=scope-0, physicalEdgeCount=1,
> inputClassName=org.apache.tez.mapreduce.input.MRInput }}, ],
> outputSpecList=[{{ destinationVertexName=scope-28, physicalEdgeCount=0,
> outputClassName=org.apache.tez.mapreduce.output.MROutput }}, ]
> 2016-03-13 23:55:17,164 [INFO] [main] |resources.MemoryDistributor|:
> InitialMemoryDistributor (isEnabled=true) invoked with: numInputs=1,
> numOutputs=1, JVM.maxFree=1059061760,
> allocatorClassName=org.apache.tez.runtime.library.resources.WeightedScalingMemoryDistributor
> 2016-03-13 23:55:17,175 [INFO] [TezChild] |task.TezTaskRunner|: Initializing
> task, taskAttemptId=attempt_1
> 2016-03-13 23:55:17,182 [INFO] [TaskHeartbeatThread] |task.TaskReporter|:
> Routing events from heartbeat response to task,
> currentTaskAttemptId=attempt_1, eventCount=1 fromEventId=0 nextFromEventId=0
> 2016-03-13 23:55:17,212 [INFO] [I/O Setup 1 Initialize: {scope-28}]
> |Configuration.deprecation|: mapreduce.inputformat.class is deprecated.
> Instead, use mapreduce.job.inputformat.class
> 2016-03-13 23:55:17,214 [INFO] [I/O Setup 1 Initialize: {scope-28}]
> |Configuration.deprecation|: fs.default.name is deprecated. Instead, use
> fs.defaultFS
> 2016-03-13 23:55:17,223 [INFO] [I/O Setup 1 Initialize: {scope-28}]
> |counters.Limits|: Counter limits initialized with parameters:
> GROUP_NAME_MAX=256, MAX_GROUPS=1000, COUNTER_NAME_MAX=128, MAX_COUNTERS=5000
> 2016-03-13 23:55:17,228 [INFO] [I/O Setup 0 Initialize: {scope-0}]
> |input.MRInput|: scope-0 using newmapreduce API=true, split via event=true,
> numPhysicalInputs=1
> 2016-03-13 23:55:17,233 [INFO] [I/O Setup 0 Initialize: {scope-0}]
> |input.MRInput|: Initialized MRInput: scope-0
> 2016-03-13 23:55:17,345 [INFO] [TezChild] |data.SchemaTupleBackend|: Key
> [pig.schematuple] was not set... will not generate code.
> 2016-03-13 23:55:17,400 [INFO] [TezChild]
> |runtime.LogicalIOProcessorRuntimeTask|: Initialized processor
> 2016-03-13 23:55:17,400 [INFO] [TezChild]
> |runtime.LogicalIOProcessorRuntimeTask|: Waiting for 2 initializers to finish
> 2016-03-13 23:55:17,400 [INFO] [TezChild]
> |runtime.LogicalIOProcessorRuntimeTask|: Waiting for 1 initializers to finish
> 2016-03-13 23:55:17,400 [INFO] [TezChild] |task.TezTaskRunner|: Encounted an
> error while executing task: attempt_1
> java.lang.RuntimeException: could not instantiate
> 'com.twitter.elephantbird.pig.store.SequenceFileStorage' with arguments '[-c
> com.twitter.elephantbird.pig.util.TextConverter, -c
> com.twitter.elephantbird.pig.util.TextConverter]'
> at
> org.apache.pig.impl.PigContext.instantiateFuncFromSpec(PigContext.java:766)
> at
> org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POStore.getStoreFunc(POStore.java:250)
> at
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigOutputFormat.getRecordWriter(PigOutputFormat.java:76)
> at
> org.apache.pig.backend.hadoop.executionengine.tez.runtime.PigOutputFormatTez.getRecordWriter(PigOutputFormatTez.java:43)
> at
> org.apache.tez.mapreduce.output.MROutput.initialize(MROutput.java:399)
> at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask$InitializeOutputCallable._callInternal(LogicalIOProcessorRuntimeTask.java:506)
> at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask$InitializeOutputCallable.callInternal(LogicalIOProcessorRuntimeTask.java:489)
> at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask$InitializeOutputCallable.callInternal(LogicalIOProcessorRuntimeTask.java:474)
> at org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
>
[jira] [Updated] (TEZ-3165) Allow Inputs/Outputs to be initialized serially, control processor initialization relative to Inputs/Outputs
[
https://issues.apache.org/jira/browse/TEZ-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Eagles updated TEZ-3165:
-
Attachment: TEZ-3165.4.patch
Thanks for the review [~hitesh] and [~sseth]. Addressed comments and started
the commit process.
> Allow Inputs/Outputs to be initialized serially, control processor
> initialization relative to Inputs/Outputs
>
>
> Key: TEZ-3165
> URL: https://issues.apache.org/jira/browse/TEZ-3165
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Jonathan Eagles
>Assignee: Jonathan Eagles
> Attachments: TEZ-3165.1.patch, TEZ-3165.2.patch, TEZ-3165.3.patch,
> TEZ-3165.4.patch
>
>
> 2016-03-13 23:55:17,162 [INFO] [main]
> |runtime.LogicalIOProcessorRuntimeTask|: Initializing
> LogicalIOProcessorRuntimeTask with TaskSpec: DAGName :
> PigLatin:Script.pig-0_scope-0, VertexName: scope-203, VertexParallelism:
> 2707, TaskAttemptID:attempt_1,
> processorName=org.apache.pig.backend.hadoop.executionengine.tez.runtime.PigProcessor,
> inputSpecListSize=1, outputSpecListSize=1, inputSpecList=[{{
> sourceVertexName=scope-0, physicalEdgeCount=1,
> inputClassName=org.apache.tez.mapreduce.input.MRInput }}, ],
> outputSpecList=[{{ destinationVertexName=scope-28, physicalEdgeCount=0,
> outputClassName=org.apache.tez.mapreduce.output.MROutput }}, ]
> 2016-03-13 23:55:17,164 [INFO] [main] |resources.MemoryDistributor|:
> InitialMemoryDistributor (isEnabled=true) invoked with: numInputs=1,
> numOutputs=1, JVM.maxFree=1059061760,
> allocatorClassName=org.apache.tez.runtime.library.resources.WeightedScalingMemoryDistributor
> 2016-03-13 23:55:17,175 [INFO] [TezChild] |task.TezTaskRunner|: Initializing
> task, taskAttemptId=attempt_1
> 2016-03-13 23:55:17,182 [INFO] [TaskHeartbeatThread] |task.TaskReporter|:
> Routing events from heartbeat response to task,
> currentTaskAttemptId=attempt_1, eventCount=1 fromEventId=0 nextFromEventId=0
> 2016-03-13 23:55:17,212 [INFO] [I/O Setup 1 Initialize: {scope-28}]
> |Configuration.deprecation|: mapreduce.inputformat.class is deprecated.
> Instead, use mapreduce.job.inputformat.class
> 2016-03-13 23:55:17,214 [INFO] [I/O Setup 1 Initialize: {scope-28}]
> |Configuration.deprecation|: fs.default.name is deprecated. Instead, use
> fs.defaultFS
> 2016-03-13 23:55:17,223 [INFO] [I/O Setup 1 Initialize: {scope-28}]
> |counters.Limits|: Counter limits initialized with parameters:
> GROUP_NAME_MAX=256, MAX_GROUPS=1000, COUNTER_NAME_MAX=128, MAX_COUNTERS=5000
> 2016-03-13 23:55:17,228 [INFO] [I/O Setup 0 Initialize: {scope-0}]
> |input.MRInput|: scope-0 using newmapreduce API=true, split via event=true,
> numPhysicalInputs=1
> 2016-03-13 23:55:17,233 [INFO] [I/O Setup 0 Initialize: {scope-0}]
> |input.MRInput|: Initialized MRInput: scope-0
> 2016-03-13 23:55:17,345 [INFO] [TezChild] |data.SchemaTupleBackend|: Key
> [pig.schematuple] was not set... will not generate code.
> 2016-03-13 23:55:17,400 [INFO] [TezChild]
> |runtime.LogicalIOProcessorRuntimeTask|: Initialized processor
> 2016-03-13 23:55:17,400 [INFO] [TezChild]
> |runtime.LogicalIOProcessorRuntimeTask|: Waiting for 2 initializers to finish
> 2016-03-13 23:55:17,400 [INFO] [TezChild]
> |runtime.LogicalIOProcessorRuntimeTask|: Waiting for 1 initializers to finish
> 2016-03-13 23:55:17,400 [INFO] [TezChild] |task.TezTaskRunner|: Encounted an
> error while executing task: attempt_1
> java.lang.RuntimeException: could not instantiate
> 'com.twitter.elephantbird.pig.store.SequenceFileStorage' with arguments '[-c
> com.twitter.elephantbird.pig.util.TextConverter, -c
> com.twitter.elephantbird.pig.util.TextConverter]'
> at
> org.apache.pig.impl.PigContext.instantiateFuncFromSpec(PigContext.java:766)
> at
> org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POStore.getStoreFunc(POStore.java:250)
> at
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigOutputFormat.getRecordWriter(PigOutputFormat.java:76)
> at
> org.apache.pig.backend.hadoop.executionengine.tez.runtime.PigOutputFormatTez.getRecordWriter(PigOutputFormatTez.java:43)
> at
> org.apache.tez.mapreduce.output.MROutput.initialize(MROutput.java:399)
> at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask$InitializeOutputCallable._callInternal(LogicalIOProcessorRuntimeTask.java:506)
> at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask$InitializeOutputCallable.callInternal(LogicalIOProcessorRuntimeTask.java:489)
> at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask$InitializeOutputCallable.callInternal(LogicalIOProcessorRuntimeTask.java:474)
> at org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36)
> at
[jira] [Commented] (TEZ-3214) Tez UI 2: Pagination in All DAGs
[
https://issues.apache.org/jira/browse/TEZ-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241395#comment-15241395
]
TezQA commented on TEZ-3214:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12798743/TEZ-3214.1.patch
against master revision 53981d4.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified test files.
{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.dag.app.rm.TestContainerReuse
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1655//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1655//console
This message is automatically generated.
> Tez UI 2: Pagination in All DAGs
>
>
> Key: TEZ-3214
> URL: https://issues.apache.org/jira/browse/TEZ-3214
> Project: Apache Tez
> Issue Type: Sub-task
>Reporter: Sreenath Somarajapuram
>Assignee: Sreenath Somarajapuram
> Fix For: 0.8.4
>
> Attachments: TEZ-3214.1.patch
>
>
> - Row counts support a maximum of 500 DAGs.
> - Support pagination in All DAGs for querying more records than that
> supported by the row count.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: TEZ-3214 PreCommit Build #1655
Jira: https://issues.apache.org/jira/browse/TEZ-3214
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1655/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 4690 lines...]
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :tez-dag
[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/12798743/TEZ-3214.1.patch
against master revision 53981d4.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified test files.
{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.dag.app.rm.TestContainerReuse
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1655//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1655//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
cfecb2e6b45c6a726ab59b39c3f545b664da8e14 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Compressed 3.35 MB of artifacts by 27.0% relative to #1652
[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)
##
1 tests failed.
FAILED:
org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources
Error Message:
Wanted but not invoked:
taskSchedulerManagerForTest.taskAllocated(
0,
Mock for TA attempt_0_0001_0_01_04_1,
,
Container: [ContainerId: container_1_0001_01_01, NodeId: host1:0,
NodeHttpAddress: host1:0, Resource: , Priority: 1,
Token: null, ]
);
-> at
org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1272)
However, there were other interactions with this mock:
taskSchedulerManagerForTest.init(
Configuration: core-default.xml, core-site.xml, yarn-default.xml,
yarn-site.xml
);
-> at
org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1143)
taskSchedulerManagerForTest.setConfig(
Configuration: core-default.xml, core-site.xml, yarn-default.xml,
yarn-site.xml
);
-> at
org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1143)
taskSchedulerManagerForTest.serviceInit(
Configuration: core-default.xml, core-site.xml, yarn-default.xml,
yarn-site.xml
);
-> at
org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1143)
taskSchedulerManagerForTest.start();
-> at
org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1144)
taskSchedulerManagerForTest.serviceStart();
-> at
org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1144)
taskSchedulerManagerForTest.instantiateSchedulers(
"host",
0,
"",
Mock for AppContext, hashCode: 508842412
);
-> at
org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1144)
taskSchedulerManagerForTest.getContainerSignatureMatcher();
-> at
org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1144)
taskSchedulerManagerForTest.getConfig();
-> at
[jira] [Assigned] (TEZ-3213) Uncaught exception during vertex recovery leads to invalid state transition loop
[ https://issues.apache.org/jira/browse/TEZ-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger reassigned TEZ-3213: Assignee: Eric Badger > Uncaught exception during vertex recovery leads to invalid state transition > loop > > > Key: TEZ-3213 > URL: https://issues.apache.org/jira/browse/TEZ-3213 > Project: Apache Tez > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Jason Lowe >Assignee: Eric Badger > > If an uncaught exception occurs during a state transition from the RECOVERING > vertex then V_INTERNAL_ERROR will be delivered to the state machine, but that > event is not handled in the RECOVERING state. That in turn causes a > V_INTERNAL_ERROR event to be delivered to the state machine, and it loops > logging the invalid transitions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3214) Tez UI 2: Pagination in All DAGs
[ https://issues.apache.org/jira/browse/TEZ-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241352#comment-15241352 ] Hitesh Shah commented on TEZ-3214: -- (pending pre-commit ) > Tez UI 2: Pagination in All DAGs > > > Key: TEZ-3214 > URL: https://issues.apache.org/jira/browse/TEZ-3214 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Fix For: 0.8.4 > > Attachments: TEZ-3214.1.patch > > > - Row counts support a maximum of 500 DAGs. > - Support pagination in All DAGs for querying more records than that > supported by the row count. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3214) Tez UI 2: Pagination in All DAGs
[ https://issues.apache.org/jira/browse/TEZ-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241351#comment-15241351 ] Hitesh Shah commented on TEZ-3214: -- +1 > Tez UI 2: Pagination in All DAGs > > > Key: TEZ-3214 > URL: https://issues.apache.org/jira/browse/TEZ-3214 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Fix For: 0.8.4 > > Attachments: TEZ-3214.1.patch > > > - Row counts support a maximum of 500 DAGs. > - Support pagination in All DAGs for querying more records than that > supported by the row count. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3214) Tez UI 2: Pagination in All DAGs
[ https://issues.apache.org/jira/browse/TEZ-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3214: Attachment: TEZ-3214.1.patch [~hitesh] Please review. The patch adds pagination similar to UI 1, the following issues with the previous implementation are also resolved. 1. Reload on page change & row count change 2. Better UX for displaying and downloading pages 3. Display count of all downloaded pages > Tez UI 2: Pagination in All DAGs > > > Key: TEZ-3214 > URL: https://issues.apache.org/jira/browse/TEZ-3214 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Fix For: 0.8.4 > > Attachments: TEZ-3214.1.patch > > > - Row counts support a maximum of 500 DAGs. > - Support pagination in All DAGs for querying more records than that > supported by the row count. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TEZ-3214) Tez UI 2: Pagination in All DAGs
Sreenath Somarajapuram created TEZ-3214: --- Summary: Tez UI 2: Pagination in All DAGs Key: TEZ-3214 URL: https://issues.apache.org/jira/browse/TEZ-3214 Project: Apache Tez Issue Type: Sub-task Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram - Row counts support a maximum of 500 DAGs. - Support pagination in All DAGs for querying more records than that supported by the row count. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
