[jira] [Commented] (MAPREDUCE-6359) RM HA setup, Cluster tab links populated with AM hostname instead of RM

[ https://issues.apache.org/jira/browse/MAPREDUCE-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14536132#comment-14536132 ] Junping Du commented on MAPREDUCE-6359: --- Move it to MAPREDUCE project given

[jira] [Commented] (MAPREDUCE-6146) Reduce tar ball size for MR over distributed cache

[ https://issues.apache.org/jira/browse/MAPREDUCE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14535700#comment-14535700 ] Junping Du commented on MAPREDUCE-6146: --- Hi [~vinodkv], I used to run normal MR

[jira] [Updated] (MAPREDUCE-6146) Reduce tar ball size for MR over distributed cache

[ https://issues.apache.org/jira/browse/MAPREDUCE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6146: -- Status: Open (was: Patch Available) Reduce tar ball size for MR over distributed cache

[jira] [Resolved] (MAPREDUCE-6348) JobHistoryEventHandler could not flush every 30 secondes

[ https://issues.apache.org/jira/browse/MAPREDUCE-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved MAPREDUCE-6348. --- Resolution: Invalid Shouldn't be a problem because isTimerActive will set to true in the

[jira] [Commented] (MAPREDUCE-6348) JobHistoryEventHandler could not flush every 30 secondes

[ https://issues.apache.org/jira/browse/MAPREDUCE-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523444#comment-14523444 ] Junping Du commented on MAPREDUCE-6348: --- Move from YARN to MAPREDUCE.

[jira] [Moved] (MAPREDUCE-6348) JobHistoryEventHandler could not flush every 30 secondes

[ https://issues.apache.org/jira/browse/MAPREDUCE-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du moved YARN-963 to MAPREDUCE-6348: Component/s: (was: resourcemanager)

[jira] [Resolved] (MAPREDUCE-6347) TestBinaryTokenFile (and others) fail

[ https://issues.apache.org/jira/browse/MAPREDUCE-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved MAPREDUCE-6347. --- Resolution: Cannot Reproduce Move from YARN and get closed. TestBinaryTokenFile (and

[jira] [Moved] (MAPREDUCE-6347) TestBinaryTokenFile (and others) fail

[ https://issues.apache.org/jira/browse/MAPREDUCE-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du moved YARN-885 to MAPREDUCE-6347: Component/s: (was: nodemanager) Affects Version/s:

[jira] [Commented] (MAPREDUCE-6335) convert load test driver to timeline service v.2

[ https://issues.apache.org/jira/browse/MAPREDUCE-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14510052#comment-14510052 ] Junping Du commented on MAPREDUCE-6335: --- Move it inside of MAPREDUCE-6331 which

[jira] [Updated] (MAPREDUCE-6335) convert load test driver to timeline service v.2

[ https://issues.apache.org/jira/browse/MAPREDUCE-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6335: -- Issue Type: Sub-task (was: New Feature) Parent: MAPREDUCE-6331 convert load test

[jira] [Updated] (MAPREDUCE-6337) add a mode to replay MR job history files to the timeline service

[ https://issues.apache.org/jira/browse/MAPREDUCE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6337: -- Issue Type: Sub-task (was: Bug) Parent: MAPREDUCE-6331 add a mode to replay MR

[jira] [Moved] (MAPREDUCE-6337) add a mode to replay MR job history files to the timeline service

[ https://issues.apache.org/jira/browse/MAPREDUCE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du moved YARN-3438 to MAPREDUCE-6337: - Component/s: (was: timelineserver) Target Version/s:

[jira] [Updated] (MAPREDUCE-6337) add a mode to replay MR job history files to the timeline service

[ https://issues.apache.org/jira/browse/MAPREDUCE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6337: -- Target Version/s: YARN-2928 add a mode to replay MR job history files to the timeline

[jira] [Commented] (MAPREDUCE-6327) [Event producers] Implement MapReduce AM writing MR events/counters to v2 ATS

[ https://issues.apache.org/jira/browse/MAPREDUCE-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507446#comment-14507446 ] Junping Du commented on MAPREDUCE-6327: --- Hi [~vinodkv], Yes. That's right.

[jira] [Commented] (MAPREDUCE-6327) [Event producers] Implement MapReduce AM writing MR events/counters to v2 ATS

[ https://issues.apache.org/jira/browse/MAPREDUCE-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507451#comment-14507451 ] Junping Du commented on MAPREDUCE-6327: --- The reason [~zjshen] didn't choose

[jira] [Commented] (MAPREDUCE-6318) Refactor JobHistoryEventHandler for handling events in ATS v1 after YARN-2928 merge back to trunk and branch-2

[ https://issues.apache.org/jira/browse/MAPREDUCE-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506759#comment-14506759 ] Junping Du commented on MAPREDUCE-6318: --- The scope make sense. I will file a

[jira] [Commented] (MAPREDUCE-6327) [Event producers] Implement MapReduce AM writing MR events/counters to v2 ATS

[ https://issues.apache.org/jira/browse/MAPREDUCE-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506053#comment-14506053 ] Junping Du commented on MAPREDUCE-6327: --- Thanks [~zjshen] for commit this patch!

[jira] [Commented] (MAPREDUCE-6318) Refactor JobHistoryEventHandler for handling events in ATS v1 after YARN-2928 merge back to trunk and branch-2

[ https://issues.apache.org/jira/browse/MAPREDUCE-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500071#comment-14500071 ] Junping Du commented on MAPREDUCE-6318: --- May be we can add interfaces of

[jira] [Created] (MAPREDUCE-6318) Refactor JobHistoryEventHandler for handling events in ATS v1 after YARN-2928 merge back to trunk and branch-2

Junping Du created MAPREDUCE-6318: - Summary: Refactor JobHistoryEventHandler for handling events in ATS v1 after YARN-2928 merge back to trunk and branch-2 Key: MAPREDUCE-6318 URL:

[jira] [Updated] (MAPREDUCE-6189) TestMRTimelineEventHandling fails in trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6189: -- Assignee: (was: Junping Du) TestMRTimelineEventHandling fails in trunk

[jira] [Resolved] (MAPREDUCE-6189) TestMRTimelineEventHandling fails in trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved MAPREDUCE-6189. --- Resolution: Duplicate The failure get disappear when HADOOP-11815 goes in, so resolve it

[jira] [Commented] (MAPREDUCE-6189) TestMRTimelineEventHandling fails in trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485468#comment-14485468 ] Junping Du commented on MAPREDUCE-6189: --- From the log below, it get failed

[jira] [Commented] (MAPREDUCE-6189) TestMRTimelineEventHandling fails in trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485588#comment-14485588 ] Junping Du commented on MAPREDUCE-6189: --- bq. Is it failing on branch-2.7? I

[jira] [Commented] (MAPREDUCE-6189) TestMRTimelineEventHandling fails in trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485832#comment-14485832 ] Junping Du commented on MAPREDUCE-6189: --- Thanks guys for putting more thoughts

[jira] [Commented] (MAPREDUCE-6189) TestMRTimelineEventHandling fails in trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485535#comment-14485535 ] Junping Du commented on MAPREDUCE-6189: --- We do have

[jira] [Commented] (MAPREDUCE-6189) TestMRTimelineEventHandling fails in trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486225#comment-14486225 ] Junping Du commented on MAPREDUCE-6189: --- Verified the patch in MAPREDUCE-6311

[jira] [Commented] (MAPREDUCE-6293) uberized job fails with the job classloader enabled

[ https://issues.apache.org/jira/browse/MAPREDUCE-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483691#comment-14483691 ] Junping Du commented on MAPREDUCE-6293: --- Thanks [~sjlee0] for reporting the

[jira] [Commented] (MAPREDUCE-6189) TestMRTimelineEventHandling fails in trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483582#comment-14483582 ] Junping Du commented on MAPREDUCE-6189: --- I agree with [~sjlee0], reproduce on my

[jira] [Reopened] (MAPREDUCE-6189) TestMRTimelineEventHandling fails in trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reopened MAPREDUCE-6189: --- Assignee: Junping Du (was: Rohith) Reopen issue and work on it.

[jira] [Updated] (MAPREDUCE-6303) Read timeout when retrying a fetch error can be fatal to a reducer

[ https://issues.apache.org/jira/browse/MAPREDUCE-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6303: -- Resolution: Fixed Fix Version/s: 2.7.0 Hadoop Flags: Reviewed Status:

[jira] [Commented] (MAPREDUCE-6303) Read timeout when retrying a fetch error can be fatal to a reducer

[ https://issues.apache.org/jira/browse/MAPREDUCE-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392805#comment-14392805 ] Junping Du commented on MAPREDUCE-6303: --- bq. Junping Du, I would appreciate it

[jira] [Commented] (MAPREDUCE-6303) Read timeout when retrying a fetch error can be fatal to a reducer

[ https://issues.apache.org/jira/browse/MAPREDUCE-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392987#comment-14392987 ] Junping Du commented on MAPREDUCE-6303: --- +1. Patch LGTM. Will commit it shortly.

[jira] [Updated] (MAPREDUCE-6295) Fix MR resource counter to handle negative value for getting memory resource after YARN-3304

[ https://issues.apache.org/jira/browse/MAPREDUCE-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6295: -- Attachment: YARN-3304-v8.patch Update patch to address issues as comments:

[jira] [Updated] (MAPREDUCE-6295) Fix MR resource counter to handle negative value for getting memory resource after YARN-3304

[ https://issues.apache.org/jira/browse/MAPREDUCE-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6295: -- Resolution: Fixed Fix Version/s: 2.7.0 Status: Resolved (was: Patch

[jira] [Updated] (MAPREDUCE-6295) Fix MR resource counter to handle negative value for getting memory resource after YARN-3304

[ https://issues.apache.org/jira/browse/MAPREDUCE-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6295: -- Status: Patch Available (was: Open) Fix MR resource counter to handle negative value for

[jira] [Created] (MAPREDUCE-6295) Fix MR resource counter to handle negative value for getting memory resource after YARN-3304

Junping Du created MAPREDUCE-6295: - Summary: Fix MR resource counter to handle negative value for getting memory resource after YARN-3304 Key: MAPREDUCE-6295 URL:

[jira] [Updated] (MAPREDUCE-6295) Fix MR resource counter to handle negative value for getting memory resource after YARN-3304

[ https://issues.apache.org/jira/browse/MAPREDUCE-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6295: -- Attachment: YARN-3304-v6-no-rename.patch Put the patch in YARN-3304 (with fix in MR side)

[jira] [Updated] (MAPREDUCE-6295) Fix MR resource counter to handle negative value for getting memory resource after YARN-3304

[ https://issues.apache.org/jira/browse/MAPREDUCE-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6295: -- Attachment: YARN-3304-v7.patch Upload a new one. Fix MR resource counter to handle

[jira] [Commented] (MAPREDUCE-6266) Job#getTrackingURL should consistently return a proper URL

[ https://issues.apache.org/jira/browse/MAPREDUCE-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360444#comment-14360444 ] Junping Du commented on MAPREDUCE-6266: --- Can we dig out the reason why

[jira] [Commented] (MAPREDUCE-6266) Job#getTrackingURL should consistently return a proper URL

[ https://issues.apache.org/jira/browse/MAPREDUCE-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360368#comment-14360368 ] Junping Du commented on MAPREDUCE-6266: --- Thanks [~rchiang] for reporting an

[jira] [Updated] (MAPREDUCE-6263) Configurable timeout between YARNRunner terminate the application and forcefully kill.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6263: -- Summary: Configurable timeout between YARNRunner terminate the application and forcefully

[jira] [Updated] (MAPREDUCE-6263) Configurable timeout between YARNRunner terminate the application and forcefully kill.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6263: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch

[jira] [Commented] (MAPREDUCE-6263) Large jobs can lose history when killed due to brief client timeout

[ https://issues.apache.org/jira/browse/MAPREDUCE-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14353998#comment-14353998 ] Junping Du commented on MAPREDUCE-6263: --- +1. v2 patch LGTM. Will commit it

[jira] [Commented] (MAPREDUCE-6263) Large jobs can lose history when killed due to brief client timeout

[ https://issues.apache.org/jira/browse/MAPREDUCE-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14352010#comment-14352010 ] Junping Du commented on MAPREDUCE-6263: --- Thanks [~eepayne] for working on a

[jira] [Updated] (MAPREDUCE-5583) Ability to limit running map and reduce tasks

[ https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-5583: -- Resolution: Fixed Fix Version/s: 2.7.0 Hadoop Flags: Reviewed Status:

[jira] [Commented] (MAPREDUCE-5583) Ability to limit running map and reduce tasks

[ https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14344836#comment-14344836 ] Junping Du commented on MAPREDUCE-5583: --- +1. Committing it in. Ability to

[jira] [Commented] (MAPREDUCE-5583) Ability to limit running map and reduce tasks

[ https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14344331#comment-14344331 ] Junping Du commented on MAPREDUCE-5583: --- bq. As that task completes the ask will

[jira] [Commented] (MAPREDUCE-5583) Ability to limit running map and reduce tasks

[ https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340276#comment-14340276 ] Junping Du commented on MAPREDUCE-5583: --- Thanks [~jlowe] for explanation and

[jira] [Commented] (MAPREDUCE-5583) Ability to limit running map and reduce tasks

[ https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340302#comment-14340302 ] Junping Du commented on MAPREDUCE-5583: --- Filed YARN-3274 to address the issue in

[jira] [Commented] (MAPREDUCE-5583) Ability to limit running map and reduce tasks

[ https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14338866#comment-14338866 ] Junping Du commented on MAPREDUCE-5583: --- Thanks [~jlowe] for updating the patch!

[jira] [Commented] (MAPREDUCE-5583) Ability to limit running map and reduce tasks

[ https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14329662#comment-14329662 ] Junping Du commented on MAPREDUCE-5583: --- More comments should come later.

[jira] [Commented] (MAPREDUCE-5583) Ability to limit running map and reduce tasks

[ https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14329658#comment-14329658 ] Junping Du commented on MAPREDUCE-5583: --- Thanks [~jlowe] for updating the patch.

[jira] [Commented] (MAPREDUCE-6225) Fix new findbug warnings in hadoop-mapreduce-client-core

[ https://issues.apache.org/jira/browse/MAPREDUCE-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14322985#comment-14322985 ] Junping Du commented on MAPREDUCE-6225: --- +1. Latest patch LGTM. I will go ahead

[jira] [Updated] (MAPREDUCE-6225) Fix new findbug warnings in hadoop-mapreduce-client-core

[ https://issues.apache.org/jira/browse/MAPREDUCE-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6225: -- Resolution: Fixed Fix Version/s: 2.7.0 Hadoop Flags: Reviewed Status:

[jira] [Commented] (MAPREDUCE-6225) Fix new findbug warnings in hadoop-mapreduce-client-core

[ https://issues.apache.org/jira/browse/MAPREDUCE-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14322651#comment-14322651 ] Junping Du commented on MAPREDUCE-6225: --- Thanks all for good discussion here! I

[jira] [Commented] (MAPREDUCE-6225) Fix new findbug warnings in hadoop-mapreduce-client-core

[ https://issues.apache.org/jira/browse/MAPREDUCE-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14322687#comment-14322687 ] Junping Du commented on MAPREDUCE-6225: --- I would suggest not to do this at this

[jira] [Commented] (MAPREDUCE-6225) Fix new findbug warnings in hadoop-mapreduce-client-core

[ https://issues.apache.org/jira/browse/MAPREDUCE-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302687#comment-14302687 ] Junping Du commented on MAPREDUCE-6225: --- Hi [~varun_saxena], sorry for missing

[jira] [Commented] (MAPREDUCE-6225) Fix new findbug warnings in hadoop-mapreduce-client-core

[ https://issues.apache.org/jira/browse/MAPREDUCE-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295082#comment-14295082 ] Junping Du commented on MAPREDUCE-6225: --- Thanks [~varun_saxena] for delivering a

[jira] [Updated] (MAPREDUCE-6149) Document override log4j.properties in MR job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6149: -- Attachment: MAPREDUCE-6149-v3.patch Document override log4j.properties in MR job

[jira] [Commented] (MAPREDUCE-6149) Document override log4j.properties in MR job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255714#comment-14255714 ] Junping Du commented on MAPREDUCE-6149: --- Thanks [~qwertymaniac] for review and

[jira] [Commented] (MAPREDUCE-5558) Scheme for local file is lost when submitting mapreduce job using mapreduce API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14246826#comment-14246826 ] Junping Du commented on MAPREDUCE-5558: --- Hive meet the similar problem when

[jira] [Commented] (MAPREDUCE-6173) Document the configuration of deploying MR over distributed cache with enabling wired encryption at the same time

[ https://issues.apache.org/jira/browse/MAPREDUCE-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14246853#comment-14246853 ] Junping Du commented on MAPREDUCE-6173: --- The findbugs warning shouldn't be

[jira] [Updated] (MAPREDUCE-6149) Document override log4j.properties in MR job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6149: -- Attachment: MAPREDUCE-6149-v2.patch Document override log4j.properties in MR job

[jira] [Commented] (MAPREDUCE-6149) Document override log4j.properties in MR job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14246949#comment-14246949 ] Junping Du commented on MAPREDUCE-6149: --- Thanks [~qwertymaniac] for review and

[jira] [Updated] (MAPREDUCE-6149) Document override log4j.properties in MR job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6149: -- Attachment: MAPREDUCE-6149.patch Document override log4j.properties in MR job

[jira] [Updated] (MAPREDUCE-6149) Document override log4j.properties in MR job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6149: -- Status: Patch Available (was: Open) Document override log4j.properties in MR job

[jira] [Updated] (MAPREDUCE-6173) Document the configuration of deploying MR over distributed cache with enabling wired encryption at the same time

[ https://issues.apache.org/jira/browse/MAPREDUCE-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6173: -- Attachment: MAPREDUCE-6173-v2.patch Thanks [~xgong] for the review and comments! v2 patch

[jira] [Resolved] (MAPREDUCE-6168) Old MR client is still broken when receiving new counters from MR job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved MAPREDUCE-6168. --- Resolution: Won't Fix Thanks [~zjshen] and [~kasha] for comments! Looks like we already

[jira] [Commented] (MAPREDUCE-6168) Old MR client is still broken when receiving new counters from MR job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224654#comment-14224654 ] Junping Du commented on MAPREDUCE-6168: --- Hi [~zjshen], Thanks for reporting

[jira] [Commented] (MAPREDUCE-5831) Old MR client is not compatible with new MR application

[ https://issues.apache.org/jira/browse/MAPREDUCE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224663#comment-14224663 ] Junping Du commented on MAPREDUCE-5831: --- Hi [~zjshen], I think problem get fixed

[jira] [Created] (MAPREDUCE-6173) Document the configuration of deploying MR over distributed cache with enabling wired encryption at the same time

Junping Du created MAPREDUCE-6173: - Summary: Document the configuration of deploying MR over distributed cache with enabling wired encryption at the same time Key: MAPREDUCE-6173 URL:

[jira] [Updated] (MAPREDUCE-6173) Document the configuration of deploying MR over distributed cache with enabling wired encryption at the same time

[ https://issues.apache.org/jira/browse/MAPREDUCE-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6173: -- Attachment: Screen Shot for MAPREDUCE-6173.png Document the configuration of deploying MR

[jira] [Updated] (MAPREDUCE-6173) Document the configuration of deploying MR over distributed cache with enabling wired encryption at the same time

[ https://issues.apache.org/jira/browse/MAPREDUCE-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6173: -- Attachment: MAPREDUCE-6173.patch Document the configuration of deploying MR over

[jira] [Updated] (MAPREDUCE-6173) Document the configuration of deploying MR over distributed cache with enabling wired encryption at the same time

[ https://issues.apache.org/jira/browse/MAPREDUCE-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6173: -- Status: Patch Available (was: Open) Document the configuration of deploying MR over

[jira] [Commented] (MAPREDUCE-6173) Document the configuration of deploying MR over distributed cache with enabling wired encryption at the same time

[ https://issues.apache.org/jira/browse/MAPREDUCE-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224762#comment-14224762 ] Junping Du commented on MAPREDUCE-6173: --- Attach the first patch and screenshot

[jira] [Commented] (MAPREDUCE-6168) Old MR client is still broken when receiving new counters from MR job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224903#comment-14224903 ] Junping Du commented on MAPREDUCE-6168: --- Thanks for comments [~kasha]! bq. I

[jira] [Updated] (MAPREDUCE-6164) mapreduce.reduce.shuffle.fetch.retry.timeout-ms should be set to 3 minutes instead of 30 seconds by default to be consistent with other retry timeout

[ https://issues.apache.org/jira/browse/MAPREDUCE-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6164: -- Status: Patch Available (was: Open) mapreduce.reduce.shuffle.fetch.retry.timeout-ms

[jira] [Created] (MAPREDUCE-6164) mapreduce.reduce.shuffle.fetch.retry.timeout-ms should be set to 3 minutes instead of 30 seconds by default to keep insistent with other retry timeout

Junping Du created MAPREDUCE-6164: - Summary: mapreduce.reduce.shuffle.fetch.retry.timeout-ms should be set to 3 minutes instead of 30 seconds by default to keep insistent with other retry timeout Key: MAPREDUCE-6164

[jira] [Updated] (MAPREDUCE-6164) mapreduce.reduce.shuffle.fetch.retry.timeout-ms should be set to 3 minutes instead of 30 seconds by default to be consistent with other retry timeout

[ https://issues.apache.org/jira/browse/MAPREDUCE-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6164: -- Attachment: MAPREDUCE-6164.patch mapreduce.reduce.shuffle.fetch.retry.timeout-ms should be

[jira] [Commented] (MAPREDUCE-6164) mapreduce.reduce.shuffle.fetch.retry.timeout-ms should be set to 3 minutes instead of 30 seconds by default to be consistent with other retry timeout

[ https://issues.apache.org/jira/browse/MAPREDUCE-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14214751#comment-14214751 ] Junping Du commented on MAPREDUCE-6164: --- Deliver a quick patch to fix it.

[jira] [Commented] (MAPREDUCE-6157) Connect failed in shuffle (due to NM down) could break current retry logic to tolerant NM restart.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208077#comment-14208077 ] Junping Du commented on MAPREDUCE-6157: --- Marked as duplicate of MAPREDUCE-6156.

[jira] [Assigned] (MAPREDUCE-6156) Fetcher - connect() doesn't handle connection refused correctly

[ https://issues.apache.org/jira/browse/MAPREDUCE-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned MAPREDUCE-6156: - Assignee: Junping Du (was: Junping Du) Fetcher - connect() doesn't handle

[jira] [Commented] (MAPREDUCE-6156) Fetcher - connect() doesn't handle connection refused correctly

[ https://issues.apache.org/jira/browse/MAPREDUCE-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208982#comment-14208982 ] Junping Du commented on MAPREDUCE-6156: --- Thanks for review and comment, [~jlowe]

[jira] [Updated] (MAPREDUCE-6156) Fetcher - connect() doesn't handle connection refused correctly

[ https://issues.apache.org/jira/browse/MAPREDUCE-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6156: -- Attachment: MAPREDUCE-6156-v2.patch Fetcher - connect() doesn't handle connection refused

[jira] [Commented] (MAPREDUCE-6156) Fetcher - connect() doesn't handle connection refused correctly

[ https://issues.apache.org/jira/browse/MAPREDUCE-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14209036#comment-14209036 ] Junping Du commented on MAPREDUCE-6156: --- bq. We shouldn't use a tight loop in

[jira] [Updated] (MAPREDUCE-6156) Fetcher - connect() doesn't handle connection refused correctly

[ https://issues.apache.org/jira/browse/MAPREDUCE-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6156: -- Attachment: MAPREDUCE-6156-v3.patch Thanks [~sseth] for review! v3 patch addressed your

[jira] [Created] (MAPREDUCE-6157) Connect failed in shuffle (due to NM down) could break current retry logic to tolerant NM restart.

Junping Du created MAPREDUCE-6157: - Summary: Connect failed in shuffle (due to NM down) could break current retry logic to tolerant NM restart. Key: MAPREDUCE-6157 URL:

[jira] [Updated] (MAPREDUCE-6157) Connect failed in shuffle (due to NM down) could break current retry logic to tolerant NM restart.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6157: -- Attachment: MAPREDUCE-6157.patch Deliver a quick patch to fix it. Connect failed in

[jira] [Updated] (MAPREDUCE-6157) Connect failed in shuffle (due to NM down) could break current retry logic to tolerant NM restart.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6157: -- Status: Patch Available (was: Open) Connect failed in shuffle (due to NM down) could

[jira] [Commented] (MAPREDUCE-6156) Fetcher - connect() doesn't handle connection refused correctly

[ https://issues.apache.org/jira/browse/MAPREDUCE-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14207734#comment-14207734 ] Junping Du commented on MAPREDUCE-6156: --- Thanks [~sidharta-s] for reporting

[jira] [Updated] (MAPREDUCE-6157) Connect failed in shuffle (due to NM down) could break current retry logic to tolerant NM restart.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6157: -- Resolution: Duplicate Status: Resolved (was: Patch Available) Connect failed in

[jira] [Updated] (MAPREDUCE-6156) Fetcher - connect() doesn't handle connection refused correctly

[ https://issues.apache.org/jira/browse/MAPREDUCE-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6156: -- Priority: Blocker (was: Critical) Target Version/s: 2.6.0 Fetcher - connect()

[jira] [Updated] (MAPREDUCE-6156) Fetcher - connect() doesn't handle connection refused correctly

[ https://issues.apache.org/jira/browse/MAPREDUCE-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6156: -- Attachment: MAPREDUCE-6156.patch Fetcher - connect() doesn't handle connection refused

[jira] [Updated] (MAPREDUCE-6156) Fetcher - connect() doesn't handle connection refused correctly

[ https://issues.apache.org/jira/browse/MAPREDUCE-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6156: -- Status: Patch Available (was: Open) Fetcher - connect() doesn't handle connection refused

[jira] [Assigned] (MAPREDUCE-6052) Support overriding log4j.properties per job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned MAPREDUCE-6052: - Assignee: Junping Du (was: David Villegas) Support overriding log4j.properties per

[jira] [Updated] (MAPREDUCE-6146) Reduce tar ball size for MR over distributed cache

[ https://issues.apache.org/jira/browse/MAPREDUCE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6146: -- Attachment: MAPREDUCE-6146-v2.patch Reduce tar ball size for MR over distributed cache

[jira] [Commented] (MAPREDUCE-6052) Support overriding log4j.properties per job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14193689#comment-14193689 ] Junping Du commented on MAPREDUCE-6052: --- Thanks [~vinodkv] for comments! bq.

[jira] [Created] (MAPREDUCE-6149) Document override log4j.properties in MR job

Junping Du created MAPREDUCE-6149: - Summary: Document override log4j.properties in MR job Key: MAPREDUCE-6149 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6149 Project: Hadoop Map/Reduce

[jira] [Updated] (MAPREDUCE-6149) Document override log4j.properties in MR job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6149: -- Description: This new feature comes from MAPREDUCE-6052, some documentation requirements

[jira] [Resolved] (MAPREDUCE-6052) Support overriding log4j.properties per job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved MAPREDUCE-6052. --- Resolution: Fixed Support overriding log4j.properties per job

<    1   2   3   4   5   6   7   >