[jira] [Commented] (TEZ-2075) Incompatible issue caused by TEZ-1233 that TezConfiguration.TEZ_SITE_XML is made private

[ https://issues.apache.org/jira/browse/TEZ-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316125#comment-14316125 ] Jeff Zhang commented on TEZ-2075: - Create PIG-4414, wait for pig folks' comment. > Incomp

[jira] [Resolved] (TEZ-2042) TEZ-UI tez logo should link to app home page

[ https://issues.apache.org/jira/browse/TEZ-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang resolved TEZ-2042. - Resolution: Duplicate Resolved in TEZ-2052 > TEZ-UI tez logo should link to app home page > ---

[jira] [Commented] (TEZ-2081) Tez UI: need mechanism to check if app has completed

[ https://issues.apache.org/jira/browse/TEZ-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317310#comment-14317310 ] Jeff Zhang commented on TEZ-2081: - [~pramachandran] If checking app status is enabled, TEZ-2

[jira] [Updated] (TEZ-2071) TestAMRecovery should set test names for test DAGs

[ https://issues.apache.org/jira/browse/TEZ-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2071: Target Version/s: 0.5.4 (was: 0.7.0) Fix Version/s: (was: 0.7.0) 0.5.4 > Tes

[jira] [Commented] (TEZ-2071) TestAMRecovery should set test names for test DAGs

[ https://issues.apache.org/jira/browse/TEZ-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317409#comment-14317409 ] Jeff Zhang commented on TEZ-2071: - Cherry-pick to 0.5 & 0.6, also update CHANGES.txt commit

[jira] [Created] (TEZ-2084) TEZ-UI Format info is lost in diagnostics

Jeff Zhang created TEZ-2084: --- Summary: TEZ-UI Format info is lost in diagnostics Key: TEZ-2084 URL: https://issues.apache.org/jira/browse/TEZ-2084 Project: Apache Tez Issue Type: Bug Comp

[jira] [Updated] (TEZ-2084) TEZ-UI Format info is lost in diagnostics

[ https://issues.apache.org/jira/browse/TEZ-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2084: Attachment: task_attemp_log.png diag_format.png am_log.png > TEZ-UI Format inf

[jira] [Commented] (TEZ-2084) TEZ-UI Format info is lost in diagnostics

[ https://issues.apache.org/jira/browse/TEZ-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317550#comment-14317550 ] Jeff Zhang commented on TEZ-2084: - attach the screenshot of diagnostics am log , diagnostics

[jira] [Comment Edited] (TEZ-2084) TEZ-UI Format info is lost in diagnostics

[ https://issues.apache.org/jira/browse/TEZ-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317550#comment-14317550 ] Jeff Zhang edited comment on TEZ-2084 at 2/12/15 4:09 AM: -- attach t

[jira] [Updated] (TEZ-2024) TaskFinishedEvent may not be logged in recovery

[ https://issues.apache.org/jira/browse/TEZ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2024: Attachment: TEZ-2024-2.patch > TaskFinishedEvent may not be logged in recovery >

[jira] [Commented] (TEZ-2024) TaskFinishedEvent may not be logged in recovery

[ https://issues.apache.org/jira/browse/TEZ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317707#comment-14317707 ] Jeff Zhang commented on TEZ-2024: - Attach new patch both resolve TEZ-2024 & TEZ-2037. [~hit

[jira] [Updated] (TEZ-2024) TaskFinishedEvent may not be logged in recovery

[ https://issues.apache.org/jira/browse/TEZ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2024: Target Version/s: 0.6.1 (was: 0.7.0) > TaskFinishedEvent may not be logged in recovery > ---

[jira] [Updated] (TEZ-2084) TEZ-UI Stacktrace format info is lost in diagnostics

[ https://issues.apache.org/jira/browse/TEZ-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2084: Summary: TEZ-UI Stacktrace format info is lost in diagnostics (was: TEZ-UI Format info is lost in diagnostics

[jira] [Updated] (TEZ-2037) Should log TaskAttemptFinishedEvent if taskattempt is recovered to KILLED

[ https://issues.apache.org/jira/browse/TEZ-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2037: Target Version/s: 0.5.4 > Should log TaskAttemptFinishedEvent if taskattempt is recovered to KILLED >

[jira] [Updated] (TEZ-2037) Should log TaskAttemptFinishedEvent if taskattempt is recovered to KILLED

[ https://issues.apache.org/jira/browse/TEZ-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2037: Attachment: TEZ-2037-1.patch [~hitesh] Split out TEZ-2037 related patch to here and target this jira to 0.5.4

[jira] [Comment Edited] (TEZ-2037) Should log TaskAttemptFinishedEvent if taskattempt is recovered to KILLED

[ https://issues.apache.org/jira/browse/TEZ-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317745#comment-14317745 ] Jeff Zhang edited comment on TEZ-2037 at 2/12/15 7:30 AM: -- [~hitesh

[jira] [Created] (TEZ-2086) TEZ-UI Support Task/TaskAttempt level log

Jeff Zhang created TEZ-2086: --- Summary: TEZ-UI Support Task/TaskAttempt level log Key: TEZ-2086 URL: https://issues.apache.org/jira/browse/TEZ-2086 Project: Apache Tez Issue Type: Bug Com

[jira] [Created] (TEZ-2087) TEZ-UI No available log link for failed/killed Task

Jeff Zhang created TEZ-2087: --- Summary: TEZ-UI No available log link for failed/killed Task Key: TEZ-2087 URL: https://issues.apache.org/jira/browse/TEZ-2087 Project: Apache Tez Issue Type: Bug

[jira] [Commented] (TEZ-2087) TEZ-UI No available log link for failed/killed Task

[ https://issues.apache.org/jira/browse/TEZ-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317845#comment-14317845 ] Jeff Zhang commented on TEZ-2087: - attach screenshot > TEZ-UI No available log link for fai

[jira] [Updated] (TEZ-2087) TEZ-UI No available log link for failed/killed Task

[ https://issues.apache.org/jira/browse/TEZ-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2087: Attachment: failed_task.png > TEZ-UI No available log link for failed/killed Task > --

[jira] [Created] (TEZ-2088) Incorrect first task start time for vertex that is killed before any task starts

Jeff Zhang created TEZ-2088: --- Summary: Incorrect first task start time for vertex that is killed before any task starts Key: TEZ-2088 URL: https://issues.apache.org/jira/browse/TEZ-2088 Project: Apache Tez

[jira] [Commented] (TEZ-2088) Incorrect first task start time for vertex that is killed before any task starts

[ https://issues.apache.org/jira/browse/TEZ-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317899#comment-14317899 ] Jeff Zhang commented on TEZ-2088: - attach screenshot > Incorrect first task start time for

[jira] [Updated] (TEZ-2088) Incorrect first task start time for vertex that is killed before any task starts

[ https://issues.apache.org/jira/browse/TEZ-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2088: Attachment: incorrect_first_start_task.png > Incorrect first task start time for vertex that is killed before

[jira] [Created] (TEZ-2089) No log available for DAG that is killed

Jeff Zhang created TEZ-2089: --- Summary: No log available for DAG that is killed Key: TEZ-2089 URL: https://issues.apache.org/jira/browse/TEZ-2089 Project: Apache Tez Issue Type: Bug Repo

[jira] [Commented] (TEZ-2037) Should log TaskAttemptFinishedEvent if taskattempt is recovered to KILLED

[ https://issues.apache.org/jira/browse/TEZ-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318133#comment-14318133 ] Jeff Zhang commented on TEZ-2037: - [~sseth] Is the new findbugs due to TEZ-2045 ? > Should

[jira] [Commented] (TEZ-2075) Incompatible issue caused by TEZ-1233 that TezConfiguration.TEZ_SITE_XML is made private

[ https://issues.apache.org/jira/browse/TEZ-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319311#comment-14319311 ] Jeff Zhang commented on TEZ-2075: - [~sseth] Configuration.addResource(Configuration) only a

[jira] [Commented] (TEZ-2024) TaskFinishedEvent may not be logged in recovery

[ https://issues.apache.org/jira/browse/TEZ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319348#comment-14319348 ] Jeff Zhang commented on TEZ-2024: - [~hitesh] Should both of TEZ-2024 and TEZ-2037 go to 0.5

[jira] [Comment Edited] (TEZ-2024) TaskFinishedEvent may not be logged in recovery

[ https://issues.apache.org/jira/browse/TEZ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319348#comment-14319348 ] Jeff Zhang edited comment on TEZ-2024 at 2/13/15 1:03 AM: -- [~hitesh

[jira] [Commented] (TEZ-2024) TaskFinishedEvent may not be logged in recovery

[ https://issues.apache.org/jira/browse/TEZ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319421#comment-14319421 ] Jeff Zhang commented on TEZ-2024: - [~hitesh] Then TEZ-2037 would affect task_attempt's recov

[jira] [Commented] (TEZ-2037) Should log TaskAttemptFinishedEvent if taskattempt is recovered to KILLED

[ https://issues.apache.org/jira/browse/TEZ-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319441#comment-14319441 ] Jeff Zhang commented on TEZ-2037: - Committed to master & branch-0.5, new findbugs warning is

[jira] [Updated] (TEZ-2024) TaskFinishedEvent may not be logged in recovery

[ https://issues.apache.org/jira/browse/TEZ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2024: Attachment: TEZ-2024-3.patch Upload new patch, exclude the changes for TEZ-2037. Will commit it after prebuil

[jira] [Updated] (TEZ-2050) No Running Status shows for Task/TaskAttempt

[ https://issues.apache.org/jira/browse/TEZ-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2050: Attachment: task_attempt_running_status.png vertex_running_status.png > No Running Status show

[jira] [Updated] (TEZ-2050) No Running Status shows for Task/TaskAttempt

[ https://issues.apache.org/jira/browse/TEZ-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2050: Attachment: (was: running_taskattempt.png) > No Running Status shows for Task/TaskAttempt > --

[jira] [Updated] (TEZ-2086) TEZ-UI Support Task/TaskAttempt level log

[ https://issues.apache.org/jira/browse/TEZ-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2086: Description: Currently on the tez-ui, there's log link for task & task attempt. But actually it points to the

[jira] [Comment Edited] (TEZ-2037) Should log TaskAttemptFinishedEvent if taskattempt is recovered to KILLED

[ https://issues.apache.org/jira/browse/TEZ-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319441#comment-14319441 ] Jeff Zhang edited comment on TEZ-2037 at 2/13/15 3:16 AM: -- Committe

[jira] [Commented] (TEZ-2024) TaskFinishedEvent may not be logged in recovery

[ https://issues.apache.org/jira/browse/TEZ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319511#comment-14319511 ] Jeff Zhang commented on TEZ-2024: - Committed to master & branch-0.6 commit b74bab471649021c

[jira] [Commented] (TEZ-2024) TaskFinishedEvent may not be logged in recovery

[ https://issues.apache.org/jira/browse/TEZ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319542#comment-14319542 ] Jeff Zhang commented on TEZ-2024: - Commit it to master & branch-0.6 commit b74bab471649021c

[jira] [Issue Comment Deleted] (TEZ-2024) TaskFinishedEvent may not be logged in recovery

[ https://issues.apache.org/jira/browse/TEZ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2024: Comment: was deleted (was: Commit it to master & branch-0.6 commit b74bab471649021cf9e8d4f9087bfce0fa9bf757 (

[jira] [Created] (TEZ-2094) TEZ-UI Running Task/TaskAttempt are not excluded when choosing other status in the Dropdownlist

Jeff Zhang created TEZ-2094: --- Summary: TEZ-UI Running Task/TaskAttempt are not excluded when choosing other status in the Dropdownlist Key: TEZ-2094 URL: https://issues.apache.org/jira/browse/TEZ-2094 Proje

[jira] [Updated] (TEZ-2094) TEZ-UI Running Task/TaskAttempt are not excluded when choosing other status in the Dropdownlist

[ https://issues.apache.org/jira/browse/TEZ-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2094: Attachment: running_taskattempt.png running_task.png attach screenshot. [~pramachandran] [~Sre

[jira] [Created] (TEZ-2097) TEZ-UI Add dag logs

Jeff Zhang created TEZ-2097: --- Summary: TEZ-UI Add dag logs Key: TEZ-2097 URL: https://issues.apache.org/jira/browse/TEZ-2097 Project: Apache Tez Issue Type: Bug Components: UI

[jira] [Updated] (TEZ-2097) TEZ-UI Add dag logs

[ https://issues.apache.org/jira/browse/TEZ-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2097: Description: If dag fails due to AM error, there's no way to check the dag logs on tez-ui. Users have to grab

[jira] [Created] (TEZ-2099) Unnecessary FailedTask link for DAG succeeded but with failed task attempts

Jeff Zhang created TEZ-2099: --- Summary: Unnecessary FailedTask link for DAG succeeded but with failed task attempts Key: TEZ-2099 URL: https://issues.apache.org/jira/browse/TEZ-2099 Project: Apache Tez

[jira] [Updated] (TEZ-2099) Unnecessary FailedTask link for DAG succeeded but with failed task attempts

[ https://issues.apache.org/jira/browse/TEZ-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2099: Attachment: unneccesary_link.png > Unnecessary FailedTask link for DAG succeeded but with failed task attempts

[jira] [Commented] (TEZ-2093) Add events to MockDAGAppMaster and add e2e test for event routing

[ https://issues.apache.org/jira/browse/TEZ-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320031#comment-14320031 ] Jeff Zhang commented on TEZ-2093: - Comments: * Should put this in constructor or enable thi

[jira] [Commented] (TEZ-2075) Incompatible issue caused by TEZ-1233 that TezConfiguration.TEZ_SITE_XML is made private

[ https://issues.apache.org/jira/browse/TEZ-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320189#comment-14320189 ] Jeff Zhang commented on TEZ-2075: - Committed to master commit 8e8405b370f647d9a3c23faf9ef7a

[jira] [Commented] (TEZ-2059) Remove TaskEventHandler in TestDAGImpl

[ https://issues.apache.org/jira/browse/TEZ-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14321100#comment-14321100 ] Jeff Zhang commented on TEZ-2059: - bq. I believe the task event handler was added as there w

[jira] [Created] (TEZ-2107) Recovery failure in the case of Auto-reduce parallelism

Jeff Zhang created TEZ-2107: --- Summary: Recovery failure in the case of Auto-reduce parallelism Key: TEZ-2107 URL: https://issues.apache.org/jira/browse/TEZ-2107 Project: Apache Tez Issue Type: Bug

[jira] [Updated] (TEZ-2107) Recovery failure in the case of Auto-reduce parallelism

[ https://issues.apache.org/jira/browse/TEZ-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2107: Issue Type: Sub-task (was: Bug) Parent: TEZ-15 > Recovery failure in the case of Auto-reduce parallel

[jira] [Commented] (TEZ-2107) Recovery failure in the case of Auto-reduce parallelism

[ https://issues.apache.org/jira/browse/TEZ-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322307#comment-14322307 ] Jeff Zhang commented on TEZ-2107: - Link to TEZ-1019, refactor recovery code to use the norma

[jira] [Created] (TEZ-2109) Add locality info in TaskAttemptStartedEvent

Jeff Zhang created TEZ-2109: --- Summary: Add locality info in TaskAttemptStartedEvent Key: TEZ-2109 URL: https://issues.apache.org/jira/browse/TEZ-2109 Project: Apache Tez Issue Type: Sub-task

[jira] [Created] (TEZ-2108) Add locality on the tez-ui

Jeff Zhang created TEZ-2108: --- Summary: Add locality on the tez-ui Key: TEZ-2108 URL: https://issues.apache.org/jira/browse/TEZ-2108 Project: Apache Tez Issue Type: Bug Reporter: Jeff Zh

[jira] [Created] (TEZ-2110) Display locality info on tez-ui

Jeff Zhang created TEZ-2110: --- Summary: Display locality info on tez-ui Key: TEZ-2110 URL: https://issues.apache.org/jira/browse/TEZ-2110 Project: Apache Tez Issue Type: Bug Components: UI

[jira] [Created] (TEZ-2111) Show duration histogram of TaskAttempt on tez-ui

Jeff Zhang created TEZ-2111: --- Summary: Show duration histogram of TaskAttempt on tez-ui Key: TEZ-2111 URL: https://issues.apache.org/jira/browse/TEZ-2111 Project: Apache Tez Issue Type: Bug

[jira] [Updated] (TEZ-2110) Display locality info on tez-ui

[ https://issues.apache.org/jira/browse/TEZ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2110: Issue Type: Sub-task (was: Bug) Parent: TEZ-2108 > Display locality info on tez-ui >

[jira] [Updated] (TEZ-2110) Display locality info on tez-ui

[ https://issues.apache.org/jira/browse/TEZ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2110: Description: May also show locality statistics at vertex level on vertex view. > Display locality info on tez

[jira] [Commented] (TEZ-2038) TEZ-UI DAG is always running in tez-ui when the app is failed but no DAGFinishedEvent is logged

[ https://issues.apache.org/jira/browse/TEZ-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322694#comment-14322694 ] Jeff Zhang commented on TEZ-2038: - On behave of [~pramachandran] Committed to master & branc

[jira] [Comment Edited] (TEZ-2038) TEZ-UI DAG is always running in tez-ui when the app is failed but no DAGFinishedEvent is logged

[ https://issues.apache.org/jira/browse/TEZ-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322694#comment-14322694 ] Jeff Zhang edited comment on TEZ-2038 at 2/17/15 2:32 AM: -- On behal

[jira] [Commented] (TEZ-1972) Visualize Vertex Group as subgraph

[ https://issues.apache.org/jira/browse/TEZ-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337841#comment-14337841 ] Jeff Zhang commented on TEZ-1972: - Graphviz don't support subgraph overlapping, so there wil

[jira] [Comment Edited] (TEZ-1972) Visualize Vertex Group as subgraph

[ https://issues.apache.org/jira/browse/TEZ-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337841#comment-14337841 ] Jeff Zhang edited comment on TEZ-1972 at 2/26/15 4:13 AM: -- Graphviz

[jira] [Resolved] (TEZ-1972) Visualize Vertex Group as subgraph

[ https://issues.apache.org/jira/browse/TEZ-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang resolved TEZ-1972. - Resolution: Won't Fix > Visualize Vertex Group as subgraph > -- > >

[jira] [Updated] (TEZ-391) SharedEdge - Support for passing same output from a vertex as input to two different vertices

[ https://issues.apache.org/jira/browse/TEZ-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-391: --- Attachment: TEZ-391-WIP-4.patch > SharedEdge - Support for passing same output from a vertex as input to two > d

[jira] [Commented] (TEZ-1019) Re-factor routing of events to use common code path for normal and recovery flow.

[ https://issues.apache.org/jira/browse/TEZ-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338228#comment-14338228 ] Jeff Zhang commented on TEZ-1019: - [~hitesh] Thanks for review, attach new patch to address

[jira] [Commented] (TEZ-2148) Slow container grabbing with Capacity Scheduler in comparision to MapReduce

[ https://issues.apache.org/jira/browse/TEZ-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338269#comment-14338269 ] Jeff Zhang commented on TEZ-2148: - Quickly go through the logs, and found that tez use 280 c

[jira] [Updated] (TEZ-2148) Slow container grabbing with Capacity Scheduler in comparision to MapReduce

[ https://issues.apache.org/jira/browse/TEZ-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2148: Attachment: dag4.pdf dag3.pdf dag2.pdf dag1.pdf attach the 4 d

[jira] [Commented] (TEZ-2070) Controller class of output should be committer rather than initializer in DAG's dot file

[ https://issues.apache.org/jira/browse/TEZ-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339647#comment-14339647 ] Jeff Zhang commented on TEZ-2070: - [~hitesh] Thanks for review, committed to master. commit

[jira] [Commented] (TEZ-2148) Slow container grabbing with Capacity Scheduler in comparision to MapReduce

[ https://issues.apache.org/jira/browse/TEZ-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339678#comment-14339678 ] Jeff Zhang commented on TEZ-2148: - [~oae] Does this only happen for Capacity Scheduler ? I d

[jira] [Updated] (TEZ-1909) Remove need to copy over all events from attempt 1 to attempt 2 dir

[ https://issues.apache.org/jira/browse/TEZ-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1909: Attachment: TEZ-1909-1.patch > Remove need to copy over all events from attempt 1 to attempt 2 dir > -

[jira] [Commented] (TEZ-1909) Remove need to copy over all events from attempt 1 to attempt 2 dir

[ https://issues.apache.org/jira/browse/TEZ-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340077#comment-14340077 ] Jeff Zhang commented on TEZ-1909: - Attach patch [~hitesh] please help review it. * Split th

[jira] [Comment Edited] (TEZ-1909) Remove need to copy over all events from attempt 1 to attempt 2 dir

[ https://issues.apache.org/jira/browse/TEZ-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340077#comment-14340077 ] Jeff Zhang edited comment on TEZ-1909 at 2/27/15 12:26 PM: --- Attach

[jira] [Assigned] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang reassigned TEZ-2162: --- Assignee: Jeff Zhang > org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not > recogn

[jira] [Updated] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2162: Priority: Critical (was: Major) > org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not > r

[jira] [Updated] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2162: Attachment: TEZ-2162-1.patch Attach the patch. > org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFo

[jira] [Comment Edited] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342683#comment-14342683 ] Jeff Zhang edited comment on TEZ-2162 at 3/2/15 3:54 AM: - Attach the

[jira] [Commented] (TEZ-2110) Display locality info on tez-ui

[ https://issues.apache.org/jira/browse/TEZ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344168#comment-14344168 ] Jeff Zhang commented on TEZ-2110: - I mean add locality info for each task attempt, and provi

[jira] [Assigned] (TEZ-2163) Task status update should be handled in the START_WAIT state

[ https://issues.apache.org/jira/browse/TEZ-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang reassigned TEZ-2163: --- Assignee: Jeff Zhang > Task status update should be handled in the START_WAIT state > -

[jira] [Updated] (TEZ-2163) Task status update should be handled in the START_WAIT state

[ https://issues.apache.org/jira/browse/TEZ-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2163: Attachment: TEZ-2163-1.patch Upload patch to address this issue, besides also remove some unnecessary code in

[jira] [Commented] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346425#comment-14346425 ] Jeff Zhang commented on TEZ-2162: - [~hitesh] [~bikassaha] [~sseth] Mind review it ? > org.a

[jira] [Updated] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2162: Attachment: TEZ-2162-2.patch > org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not > recog

[jira] [Commented] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348059#comment-14348059 ] Jeff Zhang commented on TEZ-2162: - Upload new patch ( add unit test for MROutput & MROutputC

[jira] [Comment Edited] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348059#comment-14348059 ] Jeff Zhang edited comment on TEZ-2162 at 3/5/15 3:26 AM: - Upload new

[jira] [Comment Edited] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348059#comment-14348059 ] Jeff Zhang edited comment on TEZ-2162 at 3/5/15 3:26 AM: - Upload new

[jira] [Comment Edited] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348059#comment-14348059 ] Jeff Zhang edited comment on TEZ-2162 at 3/5/15 3:56 AM: - Upload new

[jira] [Issue Comment Deleted] (TEZ-119) The AM-RM heartbeat interval should not be static

[ https://issues.apache.org/jira/browse/TEZ-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-119: --- Comment: was deleted (was: Looks like it has been done. TEZ_AM_RM_HEARTBEAT_INTERVAL_MS_MAX is used for this. S

[jira] [Commented] (TEZ-119) The AM-RM heartbeat interval should not be static

[ https://issues.apache.org/jira/browse/TEZ-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348220#comment-14348220 ] Jeff Zhang commented on TEZ-119: Looks like it has been done. TEZ_AM_RM_HEARTBEAT_INTERVAL_M

[jira] [Commented] (TEZ-2174) Make task priority available to TaskAttemptListener

[ https://issues.apache.org/jira/browse/TEZ-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348763#comment-14348763 ] Jeff Zhang commented on TEZ-2174: - lgtm +1 > Make task priority available to TaskAttemptLi

[jira] [Commented] (TEZ-2162) org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not recognized

[ https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349650#comment-14349650 ] Jeff Zhang commented on TEZ-2162: - Thanks for review [~bikassaha] [~hitesh] [~sseth] If you

[jira] [Commented] (TEZ-2105) Totally Sorted Edge with auto-parallelism

[ https://issues.apache.org/jira/browse/TEZ-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350128#comment-14350128 ] Jeff Zhang commented on TEZ-2105: - [~shanaka.kuruwita] Glad to know you are interested in th

[jira] [Commented] (TEZ-714) OutputCommitters should not run in the main AM dispatcher thread

[ https://issues.apache.org/jira/browse/TEZ-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350167#comment-14350167 ] Jeff Zhang commented on TEZ-714: * Vertex Level Commit Add one new state COMMITTING in the s

[jira] [Updated] (TEZ-714) OutputCommitters should not run in the main AM dispatcher thread

[ https://issues.apache.org/jira/browse/TEZ-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-714: --- Attachment: Vertex_2.pdf DAG_2.pdf TEZ-714-1.patch > OutputCommitters should not

[jira] [Commented] (TEZ-2105) Totally Sorted Edge with auto-parallelism

[ https://issues.apache.org/jira/browse/TEZ-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352029#comment-14352029 ] Jeff Zhang commented on TEZ-2105: - bq. It seems that pig is going to be migrated onto tez in

[jira] [Updated] (TEZ-2163) Task status update should be handled in the START_WAIT state

[ https://issues.apache.org/jira/browse/TEZ-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2163: Attachment: TEZ-2163-2.patch > Task status update should be handled in the START_WAIT state >

[jira] [Commented] (TEZ-2163) Task status update should be handled in the START_WAIT state

[ https://issues.apache.org/jira/browse/TEZ-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352565#comment-14352565 ] Jeff Zhang commented on TEZ-2163: - Upload new patch. In this patch, just ignore StatusUpdate

[jira] [Commented] (TEZ-1827) MiniTezCluster takes 10 minutes to shut down

[ https://issues.apache.org/jira/browse/TEZ-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352589#comment-14352589 ] Jeff Zhang commented on TEZ-1827: - * It would be better to use tez.test. for all the test co

[jira] [Resolved] (TEZ-2100) Fix findbug issue in TaskAttemptListenerImpTezDag.getTask

[ https://issues.apache.org/jira/browse/TEZ-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang resolved TEZ-2100. - Resolution: Won't Fix It has been resolve in other jiras. > Fix findbug issue in TaskAttemptListenerImpTezD

[jira] [Commented] (TEZ-2163) Task status update should be handled in the START_WAIT state

[ https://issues.apache.org/jira/browse/TEZ-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354061#comment-14354061 ] Jeff Zhang commented on TEZ-2163: - [~sseth] Thanks for review, Should it also go to 0.5/0.6

[jira] [Commented] (TEZ-2163) Task status update should be handled in the START_WAIT state

[ https://issues.apache.org/jira/browse/TEZ-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354118#comment-14354118 ] Jeff Zhang commented on TEZ-2163: - [~sseth] Can you answer [~bikassaha]'s question on how to

[jira] [Created] (TEZ-2188) Verify vertex with bipartite source vertex and root input in client side

Jeff Zhang created TEZ-2188: --- Summary: Verify vertex with bipartite source vertex and root input in client side Key: TEZ-2188 URL: https://issues.apache.org/jira/browse/TEZ-2188 Project: Apache Tez

[jira] [Updated] (TEZ-2188) Verify vertex with bipartite source vertex and root input in client side

[ https://issues.apache.org/jira/browse/TEZ-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2188: Attachment: TEZ-2188-1.patch Upload patch > Verify vertex with bipartite source vertex and root input in clie

[jira] [Created] (TEZ-2193) Vertex with shuffle source edge and custom vertex manager should have a predefined parallelism

Jeff Zhang created TEZ-2193: --- Summary: Vertex with shuffle source edge and custom vertex manager should have a predefined parallelism Key: TEZ-2193 URL: https://issues.apache.org/jira/browse/TEZ-2193 Projec

  1   2   3   4   5   6   7   8   9   10   >