[jira] [Updated] (MAPREDUCE-2711) TestBlockPlacementPolicyRaid cannot be compiled
[
https://issues.apache.org/jira/browse/MAPREDUCE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated MAPREDUCE-2711:
--
Attachment: m2711_20110719_TestBlockPlacementPolicyRaid.java
m2711_20110719_TestBlockPlacementPolicyRaid.java: Fixed the compilation problem.
Will post a patch after HDFS-2167.
> TestBlockPlacementPolicyRaid cannot be compiled
> ---
>
> Key: MAPREDUCE-2711
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2711
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/raid
> Environment: {{TestBlockPlacementPolicyRaid}} access internal
> {{FSNamesystem}} directly. It cannot be compiled after HDFS-2147.
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
> Attachments: m2711_20110719_TestBlockPlacementPolicyRaid.java
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2709) Test case to ensure ReflectionUtils.setConf configures the target object only once
[ https://issues.apache.org/jira/browse/MAPREDUCE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudharsan Sampath updated MAPREDUCE-2709: - Resolution: Invalid Status: Resolved (was: Patch Available) The test case is moved to the common project > Test case to ensure ReflectionUtils.setConf configures the target object only > once > -- > > Key: MAPREDUCE-2709 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2709 > Project: Hadoop Map/Reduce > Issue Type: Test > Components: test >Reporter: Sudharsan Sampath > Attachments: MAPREDUCE-2709.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-2713) Recovery of ResourceManager
Recovery of ResourceManager --- Key: MAPREDUCE-2713 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2713 Project: Hadoop Map/Reduce Issue Type: New Feature Components: mrv2 Reporter: Sharad Agarwal Assignee: Mahadev konar ResourceManager needs to recover from crashes to the state where it left off. All running applications should be able to join back the restarted RM. All running containers should not be affected and continue to run. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2409) Distributed Cache does not differentiate between file /archive for files with the same path
[ https://issues.apache.org/jira/browse/MAPREDUCE-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068119#comment-13068119 ] Hadoop QA commented on MAPREDUCE-2409: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12487072/M2409_3.patch against trunk revision 1148421. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these core unit tests: org.apache.hadoop.cli.TestMRCLI org.apache.hadoop.fs.TestFileSystem -1 contrib tests. The patch failed contrib unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/484//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/484//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/484//console This message is automatically generated. > Distributed Cache does not differentiate between file /archive for files with > the same path > --- > > Key: MAPREDUCE-2409 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2409 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: distributed-cache >Affects Versions: 0.20.203.0, 0.20.203.1, 0.23.0 >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 0.20.204.0, 0.23.0 > > Attachments: M2409-0.patch, M2409-1.patch, M2409_3.patch, MR2409.patch > > > If a 'global' file is specified as a 'file' by one job - subsequent jobs > cannot override this source file to be an 'archive' (until the TT cleans up > it's cache or a TT restart). > The other way around as well -> 'archive' to 'file' > In case of an accidental submission using the wrong type - some of the tasks > for the second job will end up seeing the source file as an archive, others > as a file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2489) Jobsplits with random hostnames can make the queue unusable
[ https://issues.apache.org/jira/browse/MAPREDUCE-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Naisbitt updated MAPREDUCE-2489: Fix Version/s: 0.23.0 0.20.205.0 > Jobsplits with random hostnames can make the queue unusable > --- > > Key: MAPREDUCE-2489 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2489 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.205.0, 0.23.0 >Reporter: Jeffrey Naisbitt >Assignee: Jeffrey Naisbitt > Fix For: 0.20.205.0, 0.23.0 > > Attachments: MAPREDUCE-2489-0.20s-v2.patch, > MAPREDUCE-2489-0.20s-v3.patch, MAPREDUCE-2489-0.20s.patch, > MAPREDUCE-2489-mapred-v2.patch, MAPREDUCE-2489-mapred-v3.patch, > MAPREDUCE-2489-mapred-v4.patch, MAPREDUCE-2489-mapred.patch > > > We saw an issue where a custom InputSplit was returning invalid hostnames for > the splits that were then causing the JobTracker to attempt to excessively > resolve host names. This caused a major slowdown for the JobTracker. We > should prevent invalid InputSplit hostnames from affecting everyone else. > I propose we implement some verification for the hostnames to try to ensure > that we only do DNS lookups on valid hostnames (and fail otherwise). We > could also fail the job after a certain number of failures in the resolve. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2409) Distributed Cache does not differentiate between file /archive for files with the same path
[ https://issues.apache.org/jira/browse/MAPREDUCE-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated MAPREDUCE-2409: -- Affects Version/s: 0.23.0 Fix Version/s: 0.23.0 > Distributed Cache does not differentiate between file /archive for files with > the same path > --- > > Key: MAPREDUCE-2409 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2409 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: distributed-cache >Affects Versions: 0.20.203.0, 0.20.203.1, 0.23.0 >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 0.20.204.0, 0.23.0 > > Attachments: M2409-0.patch, M2409-1.patch, M2409_3.patch, MR2409.patch > > > If a 'global' file is specified as a 'file' by one job - subsequent jobs > cannot override this source file to be an 'archive' (until the TT cleans up > it's cache or a TT restart). > The other way around as well -> 'archive' to 'file' > In case of an accidental submission using the wrong type - some of the tasks > for the second job will end up seeing the source file as an archive, others > as a file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2409) Distributed Cache does not differentiate between file /archive for files with the same path
[ https://issues.apache.org/jira/browse/MAPREDUCE-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated MAPREDUCE-2409: -- Attachment: M2409_3.patch Thanks for the forward port Chris. This is the same as your previous trunk patch - changed to apply cleanly to the current trunk. > Distributed Cache does not differentiate between file /archive for files with > the same path > --- > > Key: MAPREDUCE-2409 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2409 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: distributed-cache >Affects Versions: 0.20.203.0, 0.20.203.1 >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 0.20.204.0 > > Attachments: M2409-0.patch, M2409-1.patch, M2409_3.patch, MR2409.patch > > > If a 'global' file is specified as a 'file' by one job - subsequent jobs > cannot override this source file to be an 'archive' (until the TT cleans up > it's cache or a TT restart). > The other way around as well -> 'archive' to 'file' > In case of an accidental submission using the wrong type - some of the tasks > for the second job will end up seeing the source file as an archive, others > as a file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2638) Create a simple stress test for the fair scheduler
[ https://issues.apache.org/jira/browse/MAPREDUCE-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068017#comment-13068017 ] Hadoop QA commented on MAPREDUCE-2638: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12485714/MAPREDUCE-2638.patch against trunk revision 1148421. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 11 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these core unit tests: org.apache.hadoop.cli.TestMRCLI org.apache.hadoop.fs.TestFileSystem org.apache.hadoop.mapred.TestDebugScript -1 contrib tests. The patch failed contrib unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/483//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/483//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/483//console This message is automatically generated. > Create a simple stress test for the fair scheduler > -- > > Key: MAPREDUCE-2638 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2638 > Project: Hadoop Map/Reduce > Issue Type: Test > Components: contrib/fair-share >Reporter: Tom White >Assignee: Tom White > Fix For: 0.23.0 > > Attachments: MAPREDUCE-2638.patch, MAPREDUCE-2638.patch > > > This would be a test that runs against a cluster, typically with settings > that allow preemption to be exercised. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2638) Create a simple stress test for the fair scheduler
[ https://issues.apache.org/jira/browse/MAPREDUCE-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom White updated MAPREDUCE-2638: - Fix Version/s: 0.23.0 Hadoop Flags: [Reviewed] Status: Patch Available (was: Open) > Create a simple stress test for the fair scheduler > -- > > Key: MAPREDUCE-2638 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2638 > Project: Hadoop Map/Reduce > Issue Type: Test > Components: contrib/fair-share >Reporter: Tom White >Assignee: Tom White > Fix For: 0.23.0 > > Attachments: MAPREDUCE-2638.patch, MAPREDUCE-2638.patch > > > This would be a test that runs against a cluster, typically with settings > that allow preemption to be exercised. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-2712) add stdin to mapdebug and reducedebug scripts in streaming
add stdin to mapdebug and reducedebug scripts in streaming -- Key: MAPREDUCE-2712 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2712 Project: Hadoop Map/Reduce Issue Type: Improvement Components: contrib/streaming Affects Versions: 0.20.2 Reporter: Antonio Piccolboni The current syntax for the mapdebug and reducedebug scripts is $script $stdout $stderr $syslog $jobconf, which seems appropriate for task failure post-analysis. But it seems more than natural to want to inspect or analyze the input to see under what input the task failed, up to rerunning the task say in debug mode or with other monitoring in place. So why not make it $script $stdin $stdout $stderr $syslog $jobconf to complete the circle? See also https://issues.apache.org/jira/browse/MAPREDUCE-2076 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2711) TestBlockPlacementPolicyRaid cannot be compiled
[
https://issues.apache.org/jira/browse/MAPREDUCE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067818#comment-13067818
]
Hudson commented on MAPREDUCE-2711:
---
Integrated in Hadoop-Mapreduce-trunk-Commit #751 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/751/])
Correct way to temporarily disable TestBlockPlacementPolicyRaid for
MAPREDUCE-2711.
szetszwo :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1148421
Files :
*
/hadoop/common/trunk/mapreduce/src/contrib/raid/src/test/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockPlacementPolicyRaid.java
> TestBlockPlacementPolicyRaid cannot be compiled
> ---
>
> Key: MAPREDUCE-2711
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2711
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/raid
> Environment: {{TestBlockPlacementPolicyRaid}} access internal
> {{FSNamesystem}} directly. It cannot be compiled after HDFS-2147.
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2711) TestBlockPlacementPolicyRaid cannot be compiled
[
https://issues.apache.org/jira/browse/MAPREDUCE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067810#comment-13067810
]
Hudson commented on MAPREDUCE-2711:
---
Integrated in Hadoop-Mapreduce-trunk-Commit #750 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/750/])
Revert r1148400 for MAPREDUCE-2711.
szetszwo :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1148416
Files :
*
/hadoop/common/trunk/mapreduce/src/contrib/raid/src/test/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockPlacementPolicyRaid.java
> TestBlockPlacementPolicyRaid cannot be compiled
> ---
>
> Key: MAPREDUCE-2711
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2711
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/raid
> Environment: {{TestBlockPlacementPolicyRaid}} access internal
> {{FSNamesystem}} directly. It cannot be compiled after HDFS-2147.
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MAPREDUCE-2710) Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for HDFS-2161
[
https://issues.apache.org/jira/browse/MAPREDUCE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE resolved MAPREDUCE-2710.
---
Resolution: Fixed
Fix Version/s: 0.23.0
Hadoop Flags: [Reviewed]
Resolving this.
> Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for
> HDFS-2161
> -
>
> Key: MAPREDUCE-2710
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2710
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
> Fix For: 0.23.0
>
> Attachments: m2710_20110719.patch
>
>
> {{DFSClient.stringifyToken(..)}} was removed by HDFS-2161.
> {{JobSubmitter.printTokens(..)}} won't be compiled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2711) TestBlockPlacementPolicyRaid cannot be compiled
[
https://issues.apache.org/jira/browse/MAPREDUCE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067800#comment-13067800
]
Hudson commented on MAPREDUCE-2711:
---
Integrated in Hadoop-Mapreduce-trunk-Commit #749 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/749/])
Temporarily disable TestBlockPlacementPolicyRaid for MAPREDUCE-2711.
szetszwo :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1148400
Files :
*
/hadoop/common/trunk/mapreduce/src/contrib/raid/src/test/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockPlacementPolicyRaid.java
> TestBlockPlacementPolicyRaid cannot be compiled
> ---
>
> Key: MAPREDUCE-2711
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2711
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/raid
> Environment: {{TestBlockPlacementPolicyRaid}} access internal
> {{FSNamesystem}} directly. It cannot be compiled after HDFS-2147.
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2711) TestBlockPlacementPolicyRaid cannot be compiled
[
https://issues.apache.org/jira/browse/MAPREDUCE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067788#comment-13067788
]
Tsz Wo (Nicholas), SZE commented on MAPREDUCE-2711:
---
I have temporarily commented out the test.
> TestBlockPlacementPolicyRaid cannot be compiled
> ---
>
> Key: MAPREDUCE-2711
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2711
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/raid
> Environment: {{TestBlockPlacementPolicyRaid}} access internal
> {{FSNamesystem}} directly. It cannot be compiled after HDFS-2147.
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-2711) TestBlockPlacementPolicyRaid cannot be compiled
TestBlockPlacementPolicyRaid cannot be compiled
---
Key: MAPREDUCE-2711
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2711
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: contrib/raid
Environment: {{TestBlockPlacementPolicyRaid}} access internal
{{FSNamesystem}} directly. It cannot be compiled after HDFS-2147.
Reporter: Tsz Wo (Nicholas), SZE
Assignee: Tsz Wo (Nicholas), SZE
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2710) Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for HDFS-2161
[
https://issues.apache.org/jira/browse/MAPREDUCE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067780#comment-13067780
]
Harsh J commented on MAPREDUCE-2710:
Thanks for fixing this. Ran into it while writing up a test case for
MAPREDUCE-2384 :)
> Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for
> HDFS-2161
> -
>
> Key: MAPREDUCE-2710
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2710
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
> Attachments: m2710_20110719.patch
>
>
> {{DFSClient.stringifyToken(..)}} was removed by HDFS-2161.
> {{JobSubmitter.printTokens(..)}} won't be compiled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2710) Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for HDFS-2161
[
https://issues.apache.org/jira/browse/MAPREDUCE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067768#comment-13067768
]
Mahadev konar commented on MAPREDUCE-2710:
--
+1...looks good to me. I think we need a similar change in the MR-279 branch.
> Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for
> HDFS-2161
> -
>
> Key: MAPREDUCE-2710
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2710
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
> Attachments: m2710_20110719.patch
>
>
> {{DFSClient.stringifyToken(..)}} was removed by HDFS-2161.
> {{JobSubmitter.printTokens(..)}} won't be compiled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2710) Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for HDFS-2161
[
https://issues.apache.org/jira/browse/MAPREDUCE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067766#comment-13067766
]
Hudson commented on MAPREDUCE-2710:
---
Integrated in Hadoop-Mapreduce-trunk-Commit #748 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/748/])
MAPREDUCE-2710. Update JobSubmitter.printTokens(..) for HDFS-2161.
szetszwo :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1148367
Files :
*
/hadoop/common/trunk/mapreduce/src/java/org/apache/hadoop/mapreduce/JobSubmitter.java
* /hadoop/common/trunk/mapreduce/CHANGES.txt
> Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for
> HDFS-2161
> -
>
> Key: MAPREDUCE-2710
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2710
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
> Attachments: m2710_20110719.patch
>
>
> {{DFSClient.stringifyToken(..)}} was removed by HDFS-2161.
> {{JobSubmitter.printTokens(..)}} won't be compiled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2710) Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for HDFS-2161
[
https://issues.apache.org/jira/browse/MAPREDUCE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067758#comment-13067758
]
Tsz Wo (Nicholas), SZE commented on MAPREDUCE-2710:
---
I tested it manually. I have temporarily committed it, otherwise, mapreduce
cannot be compiled. Will wait for a +1 before resolving this.
> Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for
> HDFS-2161
> -
>
> Key: MAPREDUCE-2710
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2710
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
> Attachments: m2710_20110719.patch
>
>
> {{DFSClient.stringifyToken(..)}} was removed by HDFS-2161.
> {{JobSubmitter.printTokens(..)}} won't be compiled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2710) Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for HDFS-2161
[
https://issues.apache.org/jira/browse/MAPREDUCE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated MAPREDUCE-2710:
--
Attachment: m2710_20110719.patch
m2710_20110719.patch: fixed the compilation problem.
> Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for
> HDFS-2161
> -
>
> Key: MAPREDUCE-2710
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2710
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
> Attachments: m2710_20110719.patch
>
>
> {{DFSClient.stringifyToken(..)}} was removed by HDFS-2161.
> {{JobSubmitter.printTokens(..)}} won't be compiled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-2710) Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for HDFS-2161
Update DFSClient.stringifyToken(..) in JobSubmitter.printTokens(..) for
HDFS-2161
-
Key: MAPREDUCE-2710
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2710
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Tsz Wo (Nicholas), SZE
Assignee: Tsz Wo (Nicholas), SZE
{{DFSClient.stringifyToken(..)}} was removed by HDFS-2161.
{{JobSubmitter.printTokens(..)}} won't be compiled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2584) Check for serializers early, and give out more information regarding missing serializers
[ https://issues.apache.org/jira/browse/MAPREDUCE-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067723#comment-13067723 ] Harsh J commented on MAPREDUCE-2584: This can run once again after HADOOP-7328 is committed. > Check for serializers early, and give out more information regarding missing > serializers > > > Key: MAPREDUCE-2584 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2584 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: task >Affects Versions: 0.20.2 >Reporter: Harsh J >Assignee: Harsh J > Labels: serializers, tasks > Fix For: 0.23.0 > > Attachments: MAPREDUCE-2584.r2.diff, MAPREDUCE-2584.r3.diff, > MAPREDUCE-2584.r4.diff > > > As discussed on HADOOP-7328, MapReduce can handle serializers in a much > better way in case of bad configuration, improper imports (Some odd Text > class instead of the Writable Text set as key), etc.. > This issue covers the MapReduce parts of the improvements (made to IFile, > MapOutputBuffer, etc. and possible early-check of serializer availability > pre-submit) that provide more information than just an NPE as is the current > case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2278) DistributedCache shouldn't hold a ref to JobConf
[ https://issues.apache.org/jira/browse/MAPREDUCE-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067713#comment-13067713 ] Abhijit Suresh Shingate commented on MAPREDUCE-2278: I guess following is the change you were referring to. Changelog for TaskTracker http://svn.apache.org/viewvc/hadoop/common/branches/branch-0.20-security-202/src/mapred/org/apache/hadoop/mapred/TaskTracker.java?view=log Revision 1077735 - (view) (download) (annotate) - [select for diffs] Modified Fri Mar 4 04:49:48 2011 UTC (4 months, 2 weeks ago) by omalley Original Path: hadoop/common/branches/branch-0.20-security-patches/src/mapred/org/apache/hadoop/mapred/TaskTracker.java File length: 137307 byte(s) Diff to previous 1077733 (colored) commit 5d38d6c838173c96f222610aaf184a50d97e08f7 Author: Chris Douglas Date: Thu Oct 7 12:11:36 2010 -0700 . Remove unnecessary reference to user configuration from TaskDistributedCacheManager causing memory leaks I guess we can close this defect in this case. > DistributedCache shouldn't hold a ref to JobConf > > > Key: MAPREDUCE-2278 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2278 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: distributed-cache, tasktracker >Affects Versions: 0.20.2 >Reporter: Arun C Murthy >Assignee: Chris Douglas > Fix For: 0.23.0 > > > The reference is unnecessary, leads to a memory leak. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-1347) Missing synchronization in MultipleOutputFormat
[ https://issues.apache.org/jira/browse/MAPREDUCE-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated MAPREDUCE-1347: --- Attachment: MAPREDUCE-1347.r7.diff Update to incorporate the HADOOP-7298 classname changes. > Missing synchronization in MultipleOutputFormat > --- > > Key: MAPREDUCE-1347 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1347 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 0.20.2, 0.21.0, 0.22.0 >Reporter: Todd Lipcon >Assignee: Harsh J > Fix For: 0.23.0 > > Attachments: MAPREDUCE-1347.r2.diff, MAPREDUCE-1347.r3.diff, > MAPREDUCE-1347.r4.diff, MAPREDUCE-1347.r5.diff, MAPREDUCE-1347.r6.diff, > MAPREDUCE-1347.r7.diff, mapreduce.1347.r1.diff > > > MultipleOutputFormat's RecordWriter implementation doesn't use > synchronization when accessing the recordWriters member. When using > multithreaded mappers or reducers, this can result in problems where two > threads will both try to create the same file, causing > AlreadyBeingCreatedException. Doing this more fine-grained than just > synchronizing the whole method is probably a good idea, so that multithreaded > mappers can actually achieve parallelism writing into separate output streams. > From what I can tell, the new API's MultipleOutputs seems not to have this > issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-1347) Missing synchronization in MultipleOutputFormat
[ https://issues.apache.org/jira/browse/MAPREDUCE-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated MAPREDUCE-1347: --- Status: In Progress (was: Patch Available) Oh oops, forgot about the blocker. Marking as in-progress. > Missing synchronization in MultipleOutputFormat > --- > > Key: MAPREDUCE-1347 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1347 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 0.21.0, 0.20.2, 0.22.0 >Reporter: Todd Lipcon >Assignee: Harsh J > Fix For: 0.23.0 > > Attachments: MAPREDUCE-1347.r2.diff, MAPREDUCE-1347.r3.diff, > MAPREDUCE-1347.r4.diff, MAPREDUCE-1347.r5.diff, MAPREDUCE-1347.r6.diff, > mapreduce.1347.r1.diff > > > MultipleOutputFormat's RecordWriter implementation doesn't use > synchronization when accessing the recordWriters member. When using > multithreaded mappers or reducers, this can result in problems where two > threads will both try to create the same file, causing > AlreadyBeingCreatedException. Doing this more fine-grained than just > synchronizing the whole method is probably a good idea, so that multithreaded > mappers can actually achieve parallelism writing into separate output streams. > From what I can tell, the new API's MultipleOutputs seems not to have this > issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-1347) Missing synchronization in MultipleOutputFormat
[ https://issues.apache.org/jira/browse/MAPREDUCE-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated MAPREDUCE-1347: --- Status: Patch Available (was: Open) Trying again, not sure what went wrong last time. > Missing synchronization in MultipleOutputFormat > --- > > Key: MAPREDUCE-1347 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1347 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 0.21.0, 0.20.2, 0.22.0 >Reporter: Todd Lipcon >Assignee: Harsh J > Fix For: 0.23.0 > > Attachments: MAPREDUCE-1347.r2.diff, MAPREDUCE-1347.r3.diff, > MAPREDUCE-1347.r4.diff, MAPREDUCE-1347.r5.diff, MAPREDUCE-1347.r6.diff, > mapreduce.1347.r1.diff > > > MultipleOutputFormat's RecordWriter implementation doesn't use > synchronization when accessing the recordWriters member. When using > multithreaded mappers or reducers, this can result in problems where two > threads will both try to create the same file, causing > AlreadyBeingCreatedException. Doing this more fine-grained than just > synchronizing the whole method is probably a good idea, so that multithreaded > mappers can actually achieve parallelism writing into separate output streams. > From what I can tell, the new API's MultipleOutputs seems not to have this > issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-1347) Missing synchronization in MultipleOutputFormat
[ https://issues.apache.org/jira/browse/MAPREDUCE-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated MAPREDUCE-1347: --- Status: Open (was: Patch Available) > Missing synchronization in MultipleOutputFormat > --- > > Key: MAPREDUCE-1347 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1347 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 0.21.0, 0.20.2, 0.22.0 >Reporter: Todd Lipcon >Assignee: Harsh J > Fix For: 0.23.0 > > Attachments: MAPREDUCE-1347.r2.diff, MAPREDUCE-1347.r3.diff, > MAPREDUCE-1347.r4.diff, MAPREDUCE-1347.r5.diff, MAPREDUCE-1347.r6.diff, > mapreduce.1347.r1.diff > > > MultipleOutputFormat's RecordWriter implementation doesn't use > synchronization when accessing the recordWriters member. When using > multithreaded mappers or reducers, this can result in problems where two > threads will both try to create the same file, causing > AlreadyBeingCreatedException. Doing this more fine-grained than just > synchronizing the whole method is probably a good idea, so that multithreaded > mappers can actually achieve parallelism writing into separate output streams. > From what I can tell, the new API's MultipleOutputs seems not to have this > issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2623) Update ClusterMapReduceTestCase to use MiniDFSCluster.Builder
[ https://issues.apache.org/jira/browse/MAPREDUCE-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067694#comment-13067694 ] Hudson commented on MAPREDUCE-2623: --- Integrated in Hadoop-Mapreduce-trunk #742 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/742/]) MAPREDUCE-2623. Update ClusterMapReduceTestCase to use MiniDFSCluster.Builder. Contributed by Harsh J Chouraria eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1147981 Files : * /hadoop/common/trunk/mapreduce/CHANGES.txt * /hadoop/common/trunk/mapreduce/src/test/mapred/org/apache/hadoop/mapred/ClusterMapReduceTestCase.java > Update ClusterMapReduceTestCase to use MiniDFSCluster.Builder > - > > Key: MAPREDUCE-2623 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2623 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: test >Affects Versions: 0.23.0 >Reporter: Jim Plush >Assignee: Harsh J >Priority: Minor > Fix For: 0.23.0 > > Attachments: MAPREDUCE-2623.r1.diff, MAPREDUCE-2623.r2.diff > > > Looking at test class ClusterMapReduceTestCase it issues a warning that the > dfsCluster = new MiniDFSCluster(conf, 2, reformatDFS, null); line of code is > deprecated and MiniDFSCluster.Builder should be used instead. It notes that > the current API will be phased out in version 24. I propose to update the > test class to the most up to date code as it's referenced several places on > the internet as an example of how to write a Hadoop Unit Test. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-1950) Jetty Acceptor can stuck TaskTracker forever
[
https://issues.apache.org/jira/browse/MAPREDUCE-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067659#comment-13067659
]
Devaraj K commented on MAPREDUCE-1950:
--
As per jetty defect [JETTY-1251|http://jira.codehaus.org/browse/JETTY-1251], it
is fixed in 6.1.25 version.
Can we upgrade to Jetty 6.1.25 or later version?
> Jetty Acceptor can stuck TaskTracker forever
>
>
> Key: MAPREDUCE-1950
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1950
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
>Affects Versions: 0.20.1
>Reporter: Scott Chen
>Assignee: Scott Chen
>
> We have observed some TaskTrackers keep getting blacklisted because of "Too
> many fetch-failure" and the logs are full of the following exception.
> There can be lots of these exceptions in one millisecond.
> {code}
> 2010-07-19 15:00:00,146 ERROR org.mortbay.log: EXCEPTION
> java.nio.channels.ClosedSelectorException
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:66)
> at sun.nio.ch.SelectorImpl.selectNow(SelectorImpl.java:88)
> at
> org.mortbay.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:630)
> at
> org.mortbay.io.nio.SelectorManager.doSelect(SelectorManager.java:191)
> at
> org.mortbay.jetty.nio.SelectChannelConnector.accept(SelectChannelConnector.java:124)
> at
> org.mortbay.jetty.AbstractConnector$Acceptor.run(AbstractConnector.java:708)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2709) Test case to ensure ReflectionUtils.setConf configures the target object only once
[ https://issues.apache.org/jira/browse/MAPREDUCE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067655#comment-13067655 ] Devaraj K commented on MAPREDUCE-2709: -- Sudharshan, As Harsh said TestReflectionUtils.java present in mapreduce project should not be expanded(and will be removed later). It is to test the backward compatibility. You can add the test code in the common project. > Test case to ensure ReflectionUtils.setConf configures the target object only > once > -- > > Key: MAPREDUCE-2709 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2709 > Project: Hadoop Map/Reduce > Issue Type: Test > Components: test >Reporter: Sudharsan Sampath > Attachments: MAPREDUCE-2709.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2709) Test case to ensure ReflectionUtils.setConf configures the target object only once
[ https://issues.apache.org/jira/browse/MAPREDUCE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067624#comment-13067624 ] Sudharsan Sampath commented on MAPREDUCE-2709: -- True. But, the api that's fixed will also be removed when we remove the mapred package in which case this test will become void. > Test case to ensure ReflectionUtils.setConf configures the target object only > once > -- > > Key: MAPREDUCE-2709 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2709 > Project: Hadoop Map/Reduce > Issue Type: Test > Components: test >Reporter: Sudharsan Sampath > Attachments: MAPREDUCE-2709.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2278) DistributedCache shouldn't hold a ref to JobConf
[ https://issues.apache.org/jira/browse/MAPREDUCE-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067619#comment-13067619 ] Abhijit Suresh Shingate commented on MAPREDUCE-2278: Hi Arun,Chris, Which hadoop version and Which part of DistributedCache code are you referring to? Thanks & Regards, Abhijit > DistributedCache shouldn't hold a ref to JobConf > > > Key: MAPREDUCE-2278 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2278 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: distributed-cache, tasktracker >Affects Versions: 0.20.2 >Reporter: Arun C Murthy >Assignee: Chris Douglas > Fix For: 0.23.0 > > > The reference is unnecessary, leads to a memory leak. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2709) Test case to ensure ReflectionUtils.setConf configures the target object only once
[ https://issues.apache.org/jira/browse/MAPREDUCE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067614#comment-13067614 ] Harsh J commented on MAPREDUCE-2709: Looks like TestReflectionUtils exists in both of the projects. The mapreduce one is just to test backward compatibility with the deprecated API components. This test should not be expanded (it will be removed later), and ideally the test should go to the common project itself. Test should be doable with any dummy class too, I should think. > Test case to ensure ReflectionUtils.setConf configures the target object only > once > -- > > Key: MAPREDUCE-2709 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2709 > Project: Hadoop Map/Reduce > Issue Type: Test > Components: test >Reporter: Sudharsan Sampath > Attachments: MAPREDUCE-2709.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2709) Test case to ensure ReflectionUtils.setConf configures the target object only once
[ https://issues.apache.org/jira/browse/MAPREDUCE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067570#comment-13067570 ] Sudharsan Sampath commented on MAPREDUCE-2709: -- Hi, I was under the same thought. But this test class existed in the mapreduce code. Also the original issue was that KeyFieldBasedPartitioner was configured twice. So I thought it will be better to test here if the patch addresses the reported bug also. If you still think it should be moved, would be happy to do that after making the code generic. > Test case to ensure ReflectionUtils.setConf configures the target object only > once > -- > > Key: MAPREDUCE-2709 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2709 > Project: Hadoop Map/Reduce > Issue Type: Test > Components: test >Reporter: Sudharsan Sampath > Attachments: MAPREDUCE-2709.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2709) Test case to ensure ReflectionUtils.setConf configures the target object only once
[ https://issues.apache.org/jira/browse/MAPREDUCE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067565#comment-13067565 ] Devaraj K commented on MAPREDUCE-2709: -- It is better to add this test code as part of the patch HADOOP-7425 in the common itself. It is testing the ReflectionUtils.java, not any mapred functionality. > Test case to ensure ReflectionUtils.setConf configures the target object only > once > -- > > Key: MAPREDUCE-2709 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2709 > Project: Hadoop Map/Reduce > Issue Type: Test > Components: test >Reporter: Sudharsan Sampath > Attachments: MAPREDUCE-2709.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2661) MR-279: Accessing MapTaskImpl from TaskImpl
[ https://issues.apache.org/jira/browse/MAPREDUCE-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharad Agarwal updated MAPREDUCE-2661: -- Resolution: Fixed Status: Resolved (was: Patch Available) I committed to MR-279 branch. Thanks Ahmed! > MR-279: Accessing MapTaskImpl from TaskImpl > --- > > Key: MAPREDUCE-2661 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2661 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Reporter: Ahmed Radwan >Assignee: Ahmed Radwan >Priority: Minor > Fix For: 0.23.0 > > Attachments: MAPREDUCE-2661.patch, MAPREDUCE-2661_rev2.patch, > MAPREDUCE-2661_rev3.patch > > > We are directly accessing MapTaskImpl in > TaskImpl.InitialScheduleTransition.transition(..). It'll be better to > reorganize the code so each subclass can provide its own behavior instead of > explicitly checking for the subclass type. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2709) Test case to ensure ReflectionUtils.setConf configures the target object only once
[ https://issues.apache.org/jira/browse/MAPREDUCE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudharsan Sampath updated MAPREDUCE-2709: - Status: Patch Available (was: Open) > Test case to ensure ReflectionUtils.setConf configures the target object only > once > -- > > Key: MAPREDUCE-2709 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2709 > Project: Hadoop Map/Reduce > Issue Type: Test > Components: test >Reporter: Sudharsan Sampath > Attachments: MAPREDUCE-2709.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2709) Test case to ensure ReflectionUtils.setConf configures the target object only once
[ https://issues.apache.org/jira/browse/MAPREDUCE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudharsan Sampath updated MAPREDUCE-2709: - Attachment: MAPREDUCE-2709.patch test case to make sure ReflectionUtils.setConf does not configure objects twice > Test case to ensure ReflectionUtils.setConf configures the target object only > once > -- > > Key: MAPREDUCE-2709 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2709 > Project: Hadoop Map/Reduce > Issue Type: Test > Components: test >Reporter: Sudharsan Sampath > Attachments: MAPREDUCE-2709.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
