You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2009/12/18 09:19:19 UTC

[jira] Created: (MAPREDUCE-1314) Some logs have wrong configuration names.

Some logs have wrong configuration names.
-----------------------------------------

                 Key: MAPREDUCE-1314
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1314
             Project: Hadoop Map/Reduce
          Issue Type: Bug
    Affects Versions: 0.21.0
            Reporter: Amareshwari Sriramadasu
            Assignee: Amareshwari Sriramadasu
             Fix For: 0.21.0


After MAPREDUCE-849, some of the logs have wrong configuration names.
For example :
09/12/16 20:30:58 INFO mapred.MapTask: mapreduce.task.mapreduce.task.io.sort.mb = 10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (MAPREDUCE-1314) Some logs have wrong configuration names.

Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796077#action_12796077 ] 

Amareshwari Sriramadasu commented on MAPREDUCE-1314:
----------------------------------------------------

bq. -1 contrib tests. 
TestStreamingExitStatus and  TestStreamingKeyValue is due to MAPREDUCE-1311, MAPREDUCE-1312.

TestSimulatorSerialJobSubmission failed with following exception, which is unrelated to the patch:
{noformat}
java.lang.RuntimeException: java.util.zip.ZipException: ZIP_Read: error reading zip file
	at org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:1600)
	at org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:1408)
	at org.apache.hadoop.conf.Configuration.getProps(Configuration.java:1352)
	at org.apache.hadoop.conf.Configuration.get(Configuration.java:574)
	at org.apache.hadoop.mapred.JobConf.checkAndWarnDeprecation(JobConf.java:1887)
	at org.apache.hadoop.mapred.JobConf.<init>(JobConf.java:347)
	at org.apache.hadoop.tools.rumen.ZombieJob.getJobConf(ZombieJob.java:123)
	at org.apache.hadoop.mapred.SimulatorJobStory.getJobConf(SimulatorJobStory.java:55)
	at org.apache.hadoop.mapred.SimulatorJobStory.getJobConf(SimulatorJobStory.java:55)
	at org.apache.hadoop.mapred.SimulatorJobInProgress.<init>(SimulatorJobInProgress.java:64)
	at org.apache.hadoop.mapred.SimulatorJobTracker.submitJob(SimulatorJobTracker.java:195)
	at org.apache.hadoop.mapred.JobTracker.submitJob(JobTracker.java:2886)
	at org.apache.hadoop.mapred.SimulatorJobClient.submitJob(SimulatorJobClient.java:352)
	at org.apache.hadoop.mapred.SimulatorJobClient.processJobSubmissionEvent(SimulatorJobClient.java:231)
	at org.apache.hadoop.mapred.SimulatorJobClient.accept(SimulatorJobClient.java:207)
	at org.apache.hadoop.mapred.MockSimulatorEngine.run(MockSimulatorEngine.java:67)
	at org.apache.hadoop.mapred.SimulatorEngine.run(SimulatorEngine.java:205)
	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
	at org.apache.hadoop.mapred.TestSimulatorEndToEnd.testMain(TestSimulatorEndToEnd.java:60)
{noformat}
The same test passed on my machine

> Some logs have wrong configuration names.
> -----------------------------------------
>
>                 Key: MAPREDUCE-1314
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1314
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: patch-1314.txt
>
>
> After MAPREDUCE-849, some of the logs have wrong configuration names.
> For example :
> 09/12/16 20:30:58 INFO mapred.MapTask: mapreduce.task.mapreduce.task.io.sort.mb = 10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (MAPREDUCE-1314) Some logs have wrong configuration names.

Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas updated MAPREDUCE-1314:
-------------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

+1

I committed this. Thanks, Amareshwari!

> Some logs have wrong configuration names.
> -----------------------------------------
>
>                 Key: MAPREDUCE-1314
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1314
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: patch-1314.txt
>
>
> After MAPREDUCE-849, some of the logs have wrong configuration names.
> For example :
> 09/12/16 20:30:58 INFO mapred.MapTask: mapreduce.task.mapreduce.task.io.sort.mb = 10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (MAPREDUCE-1314) Some logs have wrong configuration names.

Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amareshwari Sriramadasu updated MAPREDUCE-1314:
-----------------------------------------------

    Priority: Blocker  (was: Major)

> Some logs have wrong configuration names.
> -----------------------------------------
>
>                 Key: MAPREDUCE-1314
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1314
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: patch-1314.txt
>
>
> After MAPREDUCE-849, some of the logs have wrong configuration names.
> For example :
> 09/12/16 20:30:58 INFO mapred.MapTask: mapreduce.task.mapreduce.task.io.sort.mb = 10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (MAPREDUCE-1314) Some logs have wrong configuration names.

Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amareshwari Sriramadasu updated MAPREDUCE-1314:
-----------------------------------------------

    Attachment: patch-1314.txt

Patch changing all occurrences of mapreduce*mapreduce in the src.
Found all occurences by doing "egrep -iR "mapreduce\..*mapreduce\." src/" and made sure the configuration names are correct.

> Some logs have wrong configuration names.
> -----------------------------------------
>
>                 Key: MAPREDUCE-1314
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1314
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.21.0
>
>         Attachments: patch-1314.txt
>
>
> After MAPREDUCE-849, some of the logs have wrong configuration names.
> For example :
> 09/12/16 20:30:58 INFO mapred.MapTask: mapreduce.task.mapreduce.task.io.sort.mb = 10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (MAPREDUCE-1314) Some logs have wrong configuration names.

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828487#action_12828487 ] 

Hudson commented on MAPREDUCE-1314:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #225 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/225/])
    

> Some logs have wrong configuration names.
> -----------------------------------------
>
>                 Key: MAPREDUCE-1314
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1314
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: patch-1314.txt
>
>
> After MAPREDUCE-849, some of the logs have wrong configuration names.
> For example :
> 09/12/16 20:30:58 INFO mapred.MapTask: mapreduce.task.mapreduce.task.io.sort.mb = 10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (MAPREDUCE-1314) Some logs have wrong configuration names.

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804577#action_12804577 ] 

Hudson commented on MAPREDUCE-1314:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #216 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/216/])
    . Correct errant mapreduce.x.mapreduce.x replacements from
bulk change. Contributed by Amareshwari Sriramadasu


> Some logs have wrong configuration names.
> -----------------------------------------
>
>                 Key: MAPREDUCE-1314
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1314
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: patch-1314.txt
>
>
> After MAPREDUCE-849, some of the logs have wrong configuration names.
> For example :
> 09/12/16 20:30:58 INFO mapred.MapTask: mapreduce.task.mapreduce.task.io.sort.mb = 10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (MAPREDUCE-1314) Some logs have wrong configuration names.

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793591#action_12793591 ] 

Hadoop QA commented on MAPREDUCE-1314:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12428699/patch-1314.txt
  against trunk revision 893055.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 6 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 does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    -1 contrib tests.  The patch failed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/234/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/234/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/234/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/234/console

This message is automatically generated.

> Some logs have wrong configuration names.
> -----------------------------------------
>
>                 Key: MAPREDUCE-1314
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1314
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: patch-1314.txt
>
>
> After MAPREDUCE-849, some of the logs have wrong configuration names.
> For example :
> 09/12/16 20:30:58 INFO mapred.MapTask: mapreduce.task.mapreduce.task.io.sort.mb = 10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (MAPREDUCE-1314) Some logs have wrong configuration names.

Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amareshwari Sriramadasu updated MAPREDUCE-1314:
-----------------------------------------------

    Status: Patch Available  (was: Open)

> Some logs have wrong configuration names.
> -----------------------------------------
>
>                 Key: MAPREDUCE-1314
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1314
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.21.0
>
>         Attachments: patch-1314.txt
>
>
> After MAPREDUCE-849, some of the logs have wrong configuration names.
> For example :
> 09/12/16 20:30:58 INFO mapred.MapTask: mapreduce.task.mapreduce.task.io.sort.mb = 10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.