[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796741#action_12796741
]
Hudson commented on MAPREDUCE-1131:
---
Integrated in Hadoop-Mapreduce-trunk #196 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/196/])
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Fix For: 0.22.0
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch,
MAPREDUCE-1131.4.patch, MAPREDUCE-1131.5.patch, MAPREDUCE-1131.6.patch,
MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790723#action_12790723
]
Vinod K V commented on MAPREDUCE-1131:
--
Latest patch looks good to me. +1.
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch,
MAPREDUCE-1131.4.patch, MAPREDUCE-1131.5.patch, MAPREDUCE-1131.6.patch,
MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12790531#action_12790531
]
Hadoop QA commented on MAPREDUCE-1131:
--
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12427970/MAPREDUCE-1131.6.patch
against trunk revision 890531.
+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 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 passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/192/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/192/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/192/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/192/console
This message is automatically generated.
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch,
MAPREDUCE-1131.4.patch, MAPREDUCE-1131.5.patch, MAPREDUCE-1131.6.patch,
MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787433#action_12787433
]
Vinod K V commented on MAPREDUCE-1131:
--
Patch changes look good to me.
One issue with the testcase - because now we are passing an invalid agentlib,
tasks themselves are failing in the testcase, as can be expected, and so the
test takes long time to finish (the new testcase itself takes more than 3mins).
Doing the following makes the test run very fast(~30secs):
{code}
job.setMaxMapAttempts(1);
job.setMaxReduceAttempts(1);
job.setJobSetupCleanupNeeded(false);
{code}
Also, w.r.t {{TestMRJobClient}}, can you please remove the unused import of
FileNotFoundException and also convert the test into a junit 4 test?
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch,
MAPREDUCE-1131.4.patch, MAPREDUCE-1131.5.patch, MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787439#action_12787439
]
Vinod K V commented on MAPREDUCE-1131:
--
Also, now that the patch needs some update, can you also add a positive test to
verify success with hprof? We can then also verify that profile files named
like {{$attempt-id.profile}} are indeed download by the JobClient when hprof(by
default) is used.
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch,
MAPREDUCE-1131.4.patch, MAPREDUCE-1131.5.patch, MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787141#action_12787141
]
Aaron Kimball commented on MAPREDUCE-1131:
--
Todd, Vinod --
Do you have thoughts about this version of the patch?
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch,
MAPREDUCE-1131.4.patch, MAPREDUCE-1131.5.patch, MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12775287#action_12775287
]
Hadoop QA commented on MAPREDUCE-1131:
--
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12424426/MAPREDUCE-1131.5.patch
against trunk revision 834284.
+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 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 passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/131/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/131/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/131/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/131/console
This message is automatically generated.
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch,
MAPREDUCE-1131.4.patch, MAPREDUCE-1131.5.patch, MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12768503#action_12768503
]
Hadoop QA commented on MAPREDUCE-1131:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12422859/MAPREDUCE-1131.patch
against trunk revision 828081.
+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 patch appears to cause tar ant target to fail.
-1 findbugs. The patch appears to cause Findbugs to fail.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/198/testReport/
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/198/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/198/console
This message is automatically generated.
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12768512#action_12768512
]
Todd Lipcon commented on MAPREDUCE-1131:
Oops - I was thrown by the job name being the same in both cases. You should
change the job name for the second submission, I think.
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12768544#action_12768544
]
Hadoop QA commented on MAPREDUCE-1131:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12422863/MAPREDUCE-1131.2.patch
against trunk revision 828081.
+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 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-h6.grid.sp2.yahoo.net/199/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/199/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/199/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/199/console
This message is automatically generated.
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch,
MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12768546#action_12768546
]
Hadoop QA commented on MAPREDUCE-1131:
--
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12422866/MAPREDUCE-1131.3.patch
against trunk revision 828253.
+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 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 passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/88/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/88/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/88/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/88/console
This message is automatically generated.
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch,
MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12768561#action_12768561
]
Aaron Kimball commented on MAPREDUCE-1131:
--
Failure is unrelated.
Using profilers other than hprof can cause JobClient to report job failure
--
Key: MAPREDUCE-1131
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch,
MAPREDUCE-1131.patch
If task profiling is enabled, the JobClient will download the {{profile.out}}
file created by the tasks under profile. If this causes an IOException, the
job is reported as a failure to the client, even though all the tasks
themselves may complete successfully. The expected result files are assumed
to be generated by hprof. Using the profiling system with other profilers
will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
