You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2008/09/19 14:58:44 UTC
[jira] Created: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Job Restart tests take 10 minutes, can time out very easily
-----------------------------------------------------------
Key: HADOOP-4220
URL: https://issues.apache.org/jira/browse/HADOOP-4220
Project: Hadoop Core
Issue Type: Bug
Components: test
Affects Versions: 0.19.0
Reporter: Steve Loughran
HADOOP-3245 added job restart and tests for it, but the tests take a long time
TestJobTrackerRestart 667.682
TestJobTrackerRestartWithLostTracker 322.223
Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672254#action_12672254 ]
Hadoop QA commented on HADOOP-4220:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12396736/HADOOP-4220-v1.4.patch
against trunk revision 742937.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 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 Eclipse classpath. The patch retains Eclipse classpath integrity.
+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/Hadoop-Patch/3827/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3827/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3827/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3827/console
This message is automatically generated.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat reassigned HADOOP-4220:
----------------------------------
Assignee: Amar Kamat
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Attachment: HADOOP-4220-v1.4.patch
Attaching a patch updated to trunk.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672617#action_12672617 ]
Hadoop QA commented on HADOOP-4220:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12396736/HADOOP-4220-v1.4.patch
against trunk revision 743045.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 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 Eclipse classpath. The patch retains Eclipse classpath integrity.
+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 passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3832/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3832/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3832/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3832/console
This message is automatically generated.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Status: Patch Available (was: Open)
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673972#action_12673972 ]
Hudson commented on HADOOP-4220:
--------------------------------
Integrated in Hadoop-trunk #756 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/756/])
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.8.patch, HADOOP-4220-v1.9.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-4220:
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.20.0)
0.21.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Amar!
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.8.patch, HADOOP-4220-v1.9.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656098#action_12656098 ]
Tsz Wo (Nicholas), SZE commented on HADOOP-4220:
------------------------------------------------
TestJobTrackerRestart failed in hudson build #3722. See http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3722/testReport/
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Attachments: HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673004#action_12673004 ]
Hadoop QA commented on HADOOP-4220:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12400081/HADOOP-4220-v1.8.patch
against trunk revision 743513.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 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 Eclipse classpath. The patch retains Eclipse classpath integrity.
+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/Hadoop-Patch/3839/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3839/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3839/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3839/console
This message is automatically generated.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.8.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Status: Open (was: Patch Available)
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Attachment: HADOOP-4220-v1.1.patch
Attaching a patch that is updated to trunk. The test times on my box were _2 min 55 secs_ for {{TestJobTrackerRestart}} and _1 min 39 secs_ for {{TestJobTrackerRestartWithLostTracker}}.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658011#action_12658011 ]
Devaraj Das commented on HADOOP-4220:
-------------------------------------
Let's get HADOOP-4880 committed first. This patch depends on that.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Attachment: HADOOP-4220-v1.patch
Attaching a patch the brings down the runtime of {{TestJobTrackerRestart}} and {{TestJobTrackerRestartWithLostTracker}}
||Test||Run-time||
|TestJobTrackerRestart| 276.645 sec|
|TestJobTrackerRestartWithLostTracker|136.736 sec|
Trying to optimize it further.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Fix For: 0.19.0
>
> Attachments: HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Attachment: HADOOP-4220-v1.8.patch
Attaching a new patch the fixes the failure of {{TestJobTrackerRestart}}.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.8.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-4220:
--------------------------------
Status: Open (was: Patch Available)
Sorry this patch doesn't apply cleanly. Could you please generate a new patch?
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.8.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Status: Patch Available (was: Open)
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.8.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala updated HADOOP-4220:
-------------------------------------
Priority: Blocker (was: Major)
Fix Version/s: 0.20.0
Given the number of times this is failing, I think it makes sense to address this issue for Hadoop 0.20.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632687#action_12632687 ]
Amar Kamat commented on HADOOP-4220:
------------------------------------
I can think of 2 options
1) Split the test {{TestJobTrackerRestart}} into 2 test cases. Currently it comprises of 3 test cases.
2) Reduce the timeout to << 1 min
I will check if the test case can be improved further.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-4220:
--------------------------------
Fix Version/s: (was: 0.19.0)
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Attachments: HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Status: Open (was: Patch Available)
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Attachment: HADOOP-4220-v1.9.patch
Attaching a patch that applies to the trunk.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.8.patch, HADOOP-4220-v1.9.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Status: Patch Available (was: Open)
Resubmitting.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-4220:
-------------------------------
Status: Patch Available (was: Open)
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.8.patch, HADOOP-4220-v1.9.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672240#action_12672240 ]
Amareshwari Sriramadasu commented on HADOOP-4220:
-------------------------------------------------
overall patch looks good.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4220-v1.1.patch, HADOOP-4220-v1.4.patch, HADOOP-4220-v1.patch
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633209#action_12633209 ]
Steve Loughran commented on HADOOP-4220:
----------------------------------------
one cause of the delay is the 60second wait
// Wait for a minute before submitting a job
waitFor(60 * 1000);
Would it be possible to spin and poll for whatever state change is required before starting the service. Relying on delays is very brittle.
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4220) Job Restart tests take 10 minutes,
can time out very easily
Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nigel Daley updated HADOOP-4220:
--------------------------------
Fix Version/s: 0.19.0
> Job Restart tests take 10 minutes, can time out very easily
> -----------------------------------------------------------
>
> Key: HADOOP-4220
> URL: https://issues.apache.org/jira/browse/HADOOP-4220
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Amar Kamat
> Fix For: 0.19.0
>
>
> HADOOP-3245 added job restart and tests for it, but the tests take a long time
> TestJobTrackerRestart 667.682
> TestJobTrackerRestartWithLostTracker 322.223
> Something needs to be done to speed them up to keep the test cycle viable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.