[jira] [Commented] (MAPREDUCE-6838) [ATSv2 Security] Add timeline delegation token received in allocate response to UGI

[ https://issues.apache.org/jira/browse/MAPREDUCE-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136323#comment-16136323 ] Jian He commented on MAPREDUCE-6838: Yep, comment race - I just resolved this jira too. > [ATSv2

[jira] [Updated] (MAPREDUCE-6838) [ATSv2 Security] Add timeline delegation token received in allocate response to UGI

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

[jira] [Commented] (MAPREDUCE-6838) [ATSv2 Security] Add timeline delegation token received in allocate response to UGI

[ https://issues.apache.org/jira/browse/MAPREDUCE-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136305#comment-16136305 ] Jian He commented on MAPREDUCE-6838: I tried to commit to YARN-5355_branch2, but looks like

[jira] [Commented] (MAPREDUCE-6838) [ATSv2 Security] Add timeline delegation token received in allocate response to UGI

[ https://issues.apache.org/jira/browse/MAPREDUCE-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136288#comment-16136288 ] Jian He commented on MAPREDUCE-6838: bq. The code condition is correct. Will change the comment.

[jira] [Commented] (MAPREDUCE-6838) [ATSv2 Security] Add timeline delegation token received in allocate response to UGI

[ https://issues.apache.org/jira/browse/MAPREDUCE-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135858#comment-16135858 ] Jian He commented on MAPREDUCE-6838: - The comment says is OR condition where as the code is AND,

[jira] [Comment Edited] (MAPREDUCE-6838) [ATSv2 Security] Add timeline delegation token received in allocate response to UGI

[ https://issues.apache.org/jira/browse/MAPREDUCE-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134009#comment-16134009 ] Jian He edited comment on MAPREDUCE-6838 at 8/19/17 8:08 AM: - today, for

[jira] [Commented] (MAPREDUCE-6838) [ATSv2 Security] Add timeline delegation token received in allocate response to UGI

[ https://issues.apache.org/jira/browse/MAPREDUCE-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134014#comment-16134014 ] Jian He commented on MAPREDUCE-6838: Think one other way would be when we create the token service

[jira] [Comment Edited] (MAPREDUCE-6838) [ATSv2 Security] Add timeline delegation token received in allocate response to UGI

[ https://issues.apache.org/jira/browse/MAPREDUCE-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134009#comment-16134009 ] Jian He edited comment on MAPREDUCE-6838 at 8/19/17 7:57 AM: - today, for

[jira] [Comment Edited] (MAPREDUCE-6838) [ATSv2 Security] Add timeline delegation token received in allocate response to UGI

[ https://issues.apache.org/jira/browse/MAPREDUCE-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134009#comment-16134009 ] Jian He edited comment on MAPREDUCE-6838 at 8/19/17 7:56 AM: - today, for

[jira] [Commented] (MAPREDUCE-6838) [ATSv2 Security] Add timeline delegation token received in allocate response to UGI

[ https://issues.apache.org/jira/browse/MAPREDUCE-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134009#comment-16134009 ] Jian He commented on MAPREDUCE-6838: today, for other delegation tokens RMDelegationToken, the old

[jira] [Commented] (MAPREDUCE-5621) mr-jobhistory-daemon.sh doesn't have to execute mkdir and chown all the time

[ https://issues.apache.org/jira/browse/MAPREDUCE-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084298#comment-16084298 ] Jian He commented on MAPREDUCE-5621: lgtm > mr-jobhistory-daemon.sh doesn't have to execute mkdir

[jira] [Commented] (MAPREDUCE-6288) mapred job -status fails with AccessControlException

[ https://issues.apache.org/jira/browse/MAPREDUCE-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037665#comment-16037665 ] Jian He commented on MAPREDUCE-6288: [~rkanter], your last comment mentioned it is already

[jira] [Updated] (MAPREDUCE-6852) Job#updateStatus() failed with NPE due to race condition

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

[jira] [Commented] (MAPREDUCE-6852) Job#updateStatus() failed with NPE due to race condition

[ https://issues.apache.org/jira/browse/MAPREDUCE-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889376#comment-15889376 ] Jian He commented on MAPREDUCE-6852: lgtm, committing tomorrow > Job#updateStatus() failed with

[jira] [Commented] (MAPREDUCE-6852) Job#updateStatus() failed with NPE due to race condition

[ https://issues.apache.org/jira/browse/MAPREDUCE-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889206#comment-15889206 ] Jian He commented on MAPREDUCE-6852: looks like getJobID is used in the same class in several

[jira] [Comment Edited] (MAPREDUCE-6726) YARN Registry based AM discovery with retry and in-flight task persistent via JHS

[ https://issues.apache.org/jira/browse/MAPREDUCE-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522514#comment-15522514 ] Jian He edited comment on MAPREDUCE-6726 at 9/26/16 9:10 AM: -

[jira] [Commented] (MAPREDUCE-6726) YARN Registry based AM discovery with retry and in-flight task persistent via JHS

[ https://issues.apache.org/jira/browse/MAPREDUCE-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522514#comment-15522514 ] Jian He commented on MAPREDUCE-6726: [~srikanth.sampath], thanks for the patch , I looked at it.

[jira] [Commented] (MAPREDUCE-6754) Container Ids for an yarn application should be monotonically increasing in the scope of the application

[ https://issues.apache.org/jira/browse/MAPREDUCE-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436220#comment-15436220 ] Jian He commented on MAPREDUCE-6754: Thanks for the feedback, Jason, Vinod. I think we can add a

[jira] [Commented] (MAPREDUCE-6754) Container Ids for an yarn application should be monotonically increasing in the scope of the application

[ https://issues.apache.org/jira/browse/MAPREDUCE-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434421#comment-15434421 ] Jian He commented on MAPREDUCE-6754: Hi [~jlowe], mind help shedding some light on this ? any

[jira] [Updated] (MAPREDUCE-6197) Cache MapOutputLocations in ShuffleHandler

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

[jira] [Commented] (MAPREDUCE-6197) Cache MapOutputLocations in ShuffleHandler

[ https://issues.apache.org/jira/browse/MAPREDUCE-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333020#comment-15333020 ] Jian He commented on MAPREDUCE-6197: lgtm, one question is how/why do you choose such policy for

[jira] [Updated] (MAPREDUCE-6703) Add flag to allow MapReduce AM to request for OPPORTUNISTIC containers

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

[jira] [Commented] (MAPREDUCE-6703) Add flag to allow MapReduce AM to request for OPPORTUNISTIC containers

[ https://issues.apache.org/jira/browse/MAPREDUCE-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15298653#comment-15298653 ] Jian He commented on MAPREDUCE-6703: lgtm, I can commit later today if no comments from others. >

[jira] [Updated] (MAPREDUCE-6696) Add a configuration to limit the number of map tasks allowed per job.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-6696: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.9.0 Target

[jira] [Commented] (MAPREDUCE-6703) Add flag to allow MapReduce AM to request for OPPORTUNISTIC containers

[ https://issues.apache.org/jira/browse/MAPREDUCE-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292491#comment-15292491 ] Jian He commented on MAPREDUCE-6703: I see, just few minor comments: - could you add comments to

[jira] [Commented] (MAPREDUCE-6703) Add flag to allow MapReduce AM to request for OPPORTUNISTIC containers

[ https://issues.apache.org/jira/browse/MAPREDUCE-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292343#comment-15292343 ] Jian He commented on MAPREDUCE-6703: I see. depending on how locality sensitive the MR job is,

[jira] [Commented] (MAPREDUCE-6703) Add flag to allow MapReduce AM to request for OPPORTUNISTIC containers

[ https://issues.apache.org/jira/browse/MAPREDUCE-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292313#comment-15292313 ] Jian He commented on MAPREDUCE-6703: looks like the locality is ignored for opportunistic

[jira] [Commented] (MAPREDUCE-6696) Add a configuration to limit the number of map tasks allowed per job.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292106#comment-15292106 ] Jian He commented on MAPREDUCE-6696: lgtm, +1 > Add a configuration to limit the number of map

[jira] [Commented] (MAPREDUCE-6696) Add a configuration to limit the number of map tasks allowed per job.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290171#comment-15290171 ] Jian He commented on MAPREDUCE-6696: also, may be throw IllegalArgumentException instead of

[jira] [Commented] (MAPREDUCE-6696) Add a configuration to limit the number of map tasks allowed per job.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290170#comment-15290170 ] Jian He commented on MAPREDUCE-6696: I see, thanks for your explanation. patch looks good to me,

[jira] [Commented] (MAPREDUCE-6696) Add a configuration to limit the number of map tasks allowed per job.

[ https://issues.apache.org/jira/browse/MAPREDUCE-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287888#comment-15287888 ] Jian He commented on MAPREDUCE-6696: I think the MRJobConfig.NUM_MAPS is giving a hint about, not

[jira] [Updated] (MAPREDUCE-6513) MR job got hanged forever when one NM unstable for some time

[ https://issues.apache.org/jira/browse/MAPREDUCE-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-6513: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.7.3 2.8.0

[jira] [Resolved] (MAPREDUCE-6099) Adding getSplits(JobContext job, List stats) to mapreduce CombineFileInputFormat

[ https://issues.apache.org/jira/browse/MAPREDUCE-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved MAPREDUCE-6099. Resolution: Won't Fix Close as Jason mentioned > Adding getSplits(JobContext job, List

[jira] [Updated] (MAPREDUCE-4758) jobhistory web ui not showing correct # failed reducers

[ https://issues.apache.org/jira/browse/MAPREDUCE-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-4758: --- Target Version/s: 2.9.0 (was: 2.8.0) Priority: Major (was: Critical) An improvement

[jira] [Updated] (MAPREDUCE-4683) We need to fix our build to create/distribute hadoop-mapreduce-client-core-tests.jar

[ https://issues.apache.org/jira/browse/MAPREDUCE-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-4683: --- Resolution: Won't Fix Status: Resolved (was: Patch Available) I guess this could break

[jira] [Commented] (MAPREDUCE-6513) MR job got hanged forever when one NM unstable for some time

[ https://issues.apache.org/jira/browse/MAPREDUCE-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15280963#comment-15280963 ] Jian He commented on MAPREDUCE-6513: looks like TaskAttemptKillEvent will be sent twice for each

[jira] [Updated] (MAPREDUCE-6680) JHS UserLogDir scan algorithm sometime could skip directory with update in CloudFS (Azure FileSystem, S3, etc.)

[ https://issues.apache.org/jira/browse/MAPREDUCE-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-6680: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.7.3 2.8.0

[jira] [Updated] (MAPREDUCE-6619) HADOOP_CLASSPATH is overwritten in MR container

[ https://issues.apache.org/jira/browse/MAPREDUCE-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-6619: --- Resolution: Fixed Fix Version/s: 2.6.4 2.7.3 2.8.0

[jira] [Commented] (MAPREDUCE-6619) HADOOP_CLASSPATH is overwritten in MR container

[ https://issues.apache.org/jira/browse/MAPREDUCE-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15118626#comment-15118626 ] Jian He commented on MAPREDUCE-6619: lgtm , committing. > HADOOP_CLASSPATH is overwritten in MR

[jira] [Updated] (MAPREDUCE-6610) JobHistoryEventHandler should not swallow timeline response

[ https://issues.apache.org/jira/browse/MAPREDUCE-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-6610: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.8.0 Target

[jira] [Commented] (MAPREDUCE-6610) JobHistoryEventHandler should not swallow timeline response

[ https://issues.apache.org/jira/browse/MAPREDUCE-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15116339#comment-15116339 ] Jian He commented on MAPREDUCE-6610: lgtm, > JobHistoryEventHandler should not swallow timeline

[jira] [Commented] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007094#comment-15007094 ] Jian He commented on MAPREDUCE-5485: lgtm, committing > Allow repeating job commit by extending

[jira] [Commented] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007097#comment-15007097 ] Jian He commented on MAPREDUCE-5485: [~djp], there are some findbugs and ut failures, mind

[jira] [Updated] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5485: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.7.3 Target

[jira] [Commented] (MAPREDUCE-5870) Support for passing Job priority through Application Submission Context in Mapreduce Side

[ https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744709#comment-14744709 ] Jian He commented on MAPREDUCE-5870: I see, I'm ok to keep it supporting the enum as that's what I

[jira] [Commented] (MAPREDUCE-5870) Support for passing Job priority through Application Submission Context in Mapreduce Side

[ https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743154#comment-14743154 ] Jian He commented on MAPREDUCE-5870: I earlier thought we can keep backward compatible with the

[jira] [Commented] (MAPREDUCE-5870) Support for passing Job priority through Application Submission Context in Mapreduce Side

[ https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642080#comment-14642080 ] Jian He commented on MAPREDUCE-5870: [~sunilg], thanks for updating, - should we

[jira] [Commented] (MAPREDUCE-5870) Support for passing Job priority through Application Submission Context in Mapreduce Side

[ https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640790#comment-14640790 ] Jian He commented on MAPREDUCE-5870: patch looks good to me, triggering jenkins

[jira] [Updated] (MAPREDUCE-5870) Support for passing Job priority through Application Submission Context in Mapreduce Side

[ https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5870: --- Status: Patch Available (was: Open) Support for passing Job priority through Application

[jira] [Commented] (MAPREDUCE-5870) Support for passing Job priority through Application Submission Context in Mapreduce Side

[ https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641134#comment-14641134 ] Jian He commented on MAPREDUCE-5870: [~sunilg], could you check if the test

[jira] [Updated] (MAPREDUCE-6350) JobHistory doesn't support fully-functional search

[ https://issues.apache.org/jira/browse/MAPREDUCE-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-6350: --- Component/s: jobhistoryserver JobHistory doesn't support fully-functional search

[jira] [Moved] (MAPREDUCE-6350) JobHistory doesn't support fully-functional search

[ https://issues.apache.org/jira/browse/MAPREDUCE-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He moved YARN-1614 to MAPREDUCE-6350: -- Key: MAPREDUCE-6350 (was: YARN-1614) Project: Hadoop Map/Reduce

[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key

[ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296073#comment-14296073 ] Jian He commented on MAPREDUCE-6230: +1 MR AM does not survive RM restart if RM

[jira] [Updated] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key

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

[jira] [Updated] (MAPREDUCE-5568) JHS returns invalid string for reducer completion percentage if AM restarts with 0 reducer.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5568: --- Resolution: Fixed Fix Version/s: 2.7.0 Target Version/s: 2.7.0 Hadoop

[jira] [Commented] (MAPREDUCE-5785) Derive heap size or mapreduce.*.memory.mb automatically

[ https://issues.apache.org/jira/browse/MAPREDUCE-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14225462#comment-14225462 ] Jian He commented on MAPREDUCE-5785: After this patch, job somehow fails due to

[jira] [Commented] (MAPREDUCE-5568) JHS returns invalid string for reducer completion percentage if AM restarts with 0 reducer.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221569#comment-14221569 ] Jian He commented on MAPREDUCE-5568: [~minjikim], thanks for your contribution.

[jira] [Updated] (MAPREDUCE-6048) TestJavaSerialization fails in trunk build

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

[jira] [Commented] (MAPREDUCE-6126) (Rumen) Rumen tool returns error ava.lang.IllegalArgumentException: JobBuilder.process(HistoryEvent): unknown event type

[ https://issues.apache.org/jira/browse/MAPREDUCE-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14180218#comment-14180218 ] Jian He commented on MAPREDUCE-6126: make sense, +1 (Rumen) Rumen tool returns

[jira] [Updated] (MAPREDUCE-6126) (Rumen) Rumen tool returns error ava.lang.IllegalArgumentException: JobBuilder.process(HistoryEvent): unknown event type

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

[jira] [Commented] (MAPREDUCE-6126) (Rumen) Rumen tool returns error ava.lang.IllegalArgumentException: JobBuilder.process(HistoryEvent): unknown event type

[ https://issues.apache.org/jira/browse/MAPREDUCE-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179529#comment-14179529 ] Jian He commented on MAPREDUCE-6126: in JobHistoryEventHandler, seems we already

[jira] [Updated] (MAPREDUCE-6087) MRJobConfig#MR_CLIENT_TO_AM_IPC_MAX_RETRIES_ON_TIMEOUTS config name is wrong

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

[jira] [Commented] (MAPREDUCE-6087) MRJobConfig#MR_CLIENT_TO_AM_IPC_MAX_RETRIES_ON_TIMEOUTS config name is wrong

[ https://issues.apache.org/jira/browse/MAPREDUCE-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14143583#comment-14143583 ] Jian He commented on MAPREDUCE-6087: mapred-default.xml has the correct name,

[jira] [Created] (MAPREDUCE-6087) MRJobConfig#MR_CLIENT_TO_AM_IPC_MAX_RETRIES_ON_TIMEOUTS config name is wrong

Jian He created MAPREDUCE-6087: -- Summary: MRJobConfig#MR_CLIENT_TO_AM_IPC_MAX_RETRIES_ON_TIMEOUTS config name is wrong Key: MAPREDUCE-6087 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6087

[jira] [Updated] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5910: --- Status: Open (was: Patch Available) MRAppMaster should handle Resync from RM instead of

[jira] [Updated] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5910: --- Attachment: MAPREDUCE-5910.4.patch I see, thanks for investigating. added one code comment

[jira] [Updated] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5910: --- Status: Patch Available (was: Open) MRAppMaster should handle Resync from RM instead of

[jira] [Commented] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065309#comment-14065309 ] Jian He commented on MAPREDUCE-5910: committing this. MRAppMaster should handle

[jira] [Commented] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14063747#comment-14063747 ] Jian He commented on MAPREDUCE-5910: Thanks for updating the patch! patch looks

[jira] [Updated] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5910: --- Status: Patch Available (was: Open) MRAppMaster should handle Resync from RM instead of

[jira] [Commented] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14063985#comment-14063985 ] Jian He commented on MAPREDUCE-5910: Rohith, can you look into the test failures?

[jira] [Updated] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5910: --- Status: Open (was: Patch Available) MRAppMaster should handle Resync from RM instead of

[jira] [Commented] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14058156#comment-14058156 ] Jian He commented on MAPREDUCE-5910: patch looks good over all, some comments: -

[jira] [Commented] (MAPREDUCE-5924) Windows: Sort Job failed due to 'Invalid event: TA_COMMIT_PENDING at COMMIT_PENDING'

[ https://issues.apache.org/jira/browse/MAPREDUCE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14034664#comment-14034664 ] Jian He commented on MAPREDUCE-5924: LGTM， +1 Windows: Sort Job failed due to

[jira] [Commented] (MAPREDUCE-5924) Windows: Sort Job failed due to 'Invalid event: TA_COMMIT_PENDING at COMMIT_PENDING'

[ https://issues.apache.org/jira/browse/MAPREDUCE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14034668#comment-14034668 ] Jian He commented on MAPREDUCE-5924: committing.. Windows: Sort Job failed due

[jira] [Commented] (MAPREDUCE-5924) Windows: Sort Job failed due to 'Invalid event: TA_COMMIT_PENDING at COMMIT_PENDING'

[ https://issues.apache.org/jira/browse/MAPREDUCE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14034681#comment-14034681 ] Jian He commented on MAPREDUCE-5924: Zhijie, can you open jira for the exception

[jira] [Updated] (MAPREDUCE-5924) Windows: Sort Job failed due to 'Invalid event: TA_COMMIT_PENDING at COMMIT_PENDING'

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

[jira] [Updated] (MAPREDUCE-5924) Windows: Sort Job failed due to 'Invalid event: TA_COMMIT_PENDING at COMMIT_PENDING'

[ https://issues.apache.org/jira/browse/MAPREDUCE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5924: --- Fix Version/s: 2.5.0 Windows: Sort Job failed due to 'Invalid event: TA_COMMIT_PENDING at

[jira] [Commented] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

[ https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007680#comment-14007680 ] Jian He commented on MAPREDUCE-5900: Patch looks good overall. I think we need

[jira] [Created] (MAPREDUCE-5838) TestRMDelegationTokens#testRMDTMasterKeyStateOnRollingMasterKey is failing intermittently

Jian He created MAPREDUCE-5838: -- Summary: TestRMDelegationTokens#testRMDTMasterKeyStateOnRollingMasterKey is failing intermittently Key: MAPREDUCE-5838 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5838

[jira] [Updated] (MAPREDUCE-5832) TestJobClient#testGetStagingAreaDir timeout sometimes on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5832: --- Status: Patch Available (was: Open) TestJobClient#testGetStagingAreaDir timeout sometimes on

[jira] [Created] (MAPREDUCE-5832) TestJobClient fails sometimes on Windows

Jian He created MAPREDUCE-5832: -- Summary: TestJobClient fails sometimes on Windows Key: MAPREDUCE-5832 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5832 Project: Hadoop Map/Reduce Issue

[jira] [Updated] (MAPREDUCE-5832) TestJobClient fails sometimes on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5832: --- Attachment: MAPREDUCE-5832.1.patch Increased the timeout, did not find problem with the current

[jira] [Updated] (MAPREDUCE-5832) TestJobClient#testGetStagingAreaDir timeout sometimes on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5832: --- Description: java.lang.Exception: test timed out after 1000 milliseconds at

[jira] [Updated] (MAPREDUCE-5832) TestJobClient#testGetStagingAreaDir timeout sometimes on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5832: --- Summary: TestJobClient#testGetStagingAreaDir timeout sometimes on Windows (was: TestJobClient

[jira] [Commented] (MAPREDUCE-5655) Remote job submit from windows to a linux hadoop cluster fails due to wrong classpath

[ https://issues.apache.org/jira/browse/MAPREDUCE-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13964967#comment-13964967 ] Jian He commented on MAPREDUCE-5655: Please refer to MAPREDUCE-4052 for the fix,

[jira] [Updated] (MAPREDUCE-5818) hsadmin cmd is missing in mapred.cmd

[ https://issues.apache.org/jira/browse/MAPREDUCE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5818: --- Status: Patch Available (was: Open) hsadmin cmd is missing in mapred.cmd

[jira] [Created] (MAPREDUCE-5818) hsadmin cmd is missing in mapred.cmd

Jian He created MAPREDUCE-5818: -- Summary: hsadmin cmd is missing in mapred.cmd Key: MAPREDUCE-5818 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5818 Project: Hadoop Map/Reduce Issue

[jira] [Updated] (MAPREDUCE-5818) hsadmin cmd is missing in mapred.cmd

[ https://issues.apache.org/jira/browse/MAPREDUCE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5818: --- Attachment: MAPREDUCE-5818.1.patch simple patch to add the missing command hsadmin cmd is

[jira] [Updated] (MAPREDUCE-5818) hsadmin cmd is missing in mapred.cmd

[ https://issues.apache.org/jira/browse/MAPREDUCE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5818: --- Status: Patch Available (was: Open) hsadmin cmd is missing in mapred.cmd

[jira] [Updated] (MAPREDUCE-5818) hsadmin cmd is missing in mapred.cmd

[ https://issues.apache.org/jira/browse/MAPREDUCE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5818: --- Status: Open (was: Patch Available) hsadmin cmd is missing in mapred.cmd

[jira] [Updated] (MAPREDUCE-5818) hsadmin cmd is missing in mapred.cmd

[ https://issues.apache.org/jira/browse/MAPREDUCE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5818: --- Attachment: MAPREDUCE-5818.2.patch hsadmin cmd is missing in mapred.cmd

[jira] [Updated] (MAPREDUCE-5818) hsadmin cmd is missing in mapred.cmd

[ https://issues.apache.org/jira/browse/MAPREDUCE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5818: --- Status: Patch Available (was: Open) hsadmin cmd is missing in mapred.cmd

[jira] [Updated] (MAPREDUCE-5818) hsadmin cmd is missing in mapred.cmd

[ https://issues.apache.org/jira/browse/MAPREDUCE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5818: --- Status: Open (was: Patch Available) hsadmin cmd is missing in mapred.cmd

[jira] [Updated] (MAPREDUCE-5818) hsadmin cmd is missing in mapred.cmd

[ https://issues.apache.org/jira/browse/MAPREDUCE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5818: --- Attachment: (was: MAPREDUCE-5818.2.patch) hsadmin cmd is missing in mapred.cmd

[jira] [Updated] (MAPREDUCE-5818) hsadmin cmd is missing in mapred.cmd

[ https://issues.apache.org/jira/browse/MAPREDUCE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-5818: --- Attachment: MAPREDUCE-5818.3.patch hsadmin cmd is missing in mapred.cmd

[jira] [Commented] (MAPREDUCE-5816) TestMRAppMaster fails in trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954861#comment-13954861 ] Jian He commented on MAPREDUCE-5816: dup of MAPREDUCE-5815 ? TestMRAppMaster

[jira] [Commented] (MAPREDUCE-5397) AM crashes because Webapp failed to start on multi node cluster

[ https://issues.apache.org/jira/browse/MAPREDUCE-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949654#comment-13949654 ] Jian He commented on MAPREDUCE-5397: My impression on this issue was I submitted a

[jira] [Updated] (MAPREDUCE-4052) Windows eclipse cannot submit job from Windows client to Linux/Unix Hadoop cluster.

[ https://issues.apache.org/jira/browse/MAPREDUCE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-4052: --- Status: Open (was: Patch Available) Windows eclipse cannot submit job from Windows client to

[jira] [Updated] (MAPREDUCE-4052) Windows eclipse cannot submit job from Windows client to Linux/Unix Hadoop cluster.

[ https://issues.apache.org/jira/browse/MAPREDUCE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated MAPREDUCE-4052: --- Status: Patch Available (was: Open) Windows eclipse cannot submit job from Windows client to

  1   2   3   >