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 "Owen O'Malley (JIRA)" <ji...@apache.org> on 2008/02/26 19:22:51 UTC
[jira] Created: (HADOOP-2901) the job tracker should not start 2
info servers
the job tracker should not start 2 info servers
-----------------------------------------------
Key: HADOOP-2901
URL: https://issues.apache.org/jira/browse/HADOOP-2901
Project: Hadoop Core
Issue Type: Bug
Reporter: Owen O'Malley
Assignee: Amareshwari Sri Ramadasu
Priority: Blocker
Fix For: 0.17.0
The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-2901:
--------------------------------------------
Status: Open (was: Patch Available)
findbugs warning
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-2901:
--------------------------------
Status: Open (was: Patch Available)
Sorry, this patch needs to be fixed to work even when the job history is on the local file system.
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-2901:
--------------------------------------------
Attachment: patch-2901.txt
Fixed findbugs warning.
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579417#action_12579417 ]
Hudson commented on HADOOP-2901:
--------------------------------
Integrated in Hadoop-trunk #431 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/431/])
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575714#action_12575714 ]
Hadoop QA commented on HADOOP-2901:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12377248/patch-2901.txt
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler warnings.
release audit +1. The applied patch does not generate any new release audit warnings.
findbugs -1. The patch appears to introduce 1 new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1904/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1904/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1904/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1904/console
This message is automatically generated.
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-2901:
--------------------------------------------
Attachment: patch-2901.txt
This patch addresses the proposal on HADOOP-2896 and this issue.
And jsp file changes for HADOOP-2742, HADOOP-2792
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578591#action_12578591 ]
Amareshwari Sriramadasu commented on HADOOP-2901:
-------------------------------------------------
test failure is a DFS test failure, TestCopyFiles.testCopyFromLocalToDfs, due to timeout. This is not related to the patch.
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578528#action_12578528 ]
Hadoop QA commented on HADOOP-2901:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12377753/patch-2901.txt
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler warnings.
release audit +1. The applied patch does not generate any new release audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests -1. The patch failed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1956/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1956/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1956/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1956/console
This message is automatically generated.
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-2901:
--------------------------------------------
Status: Patch Available (was: Open)
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-2901:
--------------------------------------------
Status: Patch Available (was: Open)
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579173#action_12579173 ]
Hadoop QA commented on HADOOP-2901:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12377989/patch-2901.txt
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler warnings.
release audit +1. The applied patch does not generate any new release audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests -1. The patch failed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1977/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1977/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1977/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1977/console
This message is automatically generated.
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576953#action_12576953 ]
Hadoop QA commented on HADOOP-2901:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12377509/patch-2901.txt
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler warnings.
release audit +1. The applied patch does not generate any new release audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1928/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1928/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1928/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1928/console
This message is automatically generated.
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-2901:
--------------------------------
Status: Open (was: Patch Available)
A nit - can you please change the StringBuffer usages in the HistoryViewer as per the HADOOP-2996 suggestion.
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579295#action_12579295 ]
Amareshwari Sriramadasu commented on HADOOP-2901:
-------------------------------------------------
dfs.TestDFSStorageStateRecovery failed due to time out. The failure is not related to the patch
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-2901:
--------------------------------------------
Attachment: patch-2901.txt
This patch is modified to address the following:
when history is on local fs and job tracker is in initializing state, history can be accessed.
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-2901:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Amareshwari!
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-2901:
--------------------------------------------
Component/s: mapred
Affects Version/s: 0.17.0
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-2901:
--------------------------------------------
Status: Patch Available (was: Open)
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-2901:
--------------------------------------------
Status: Patch Available (was: Open)
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2901) the job tracker should not start 2
info servers
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-2901:
--------------------------------------------
Attachment: patch-2901.txt
Patch with stream buffer as suggested.
> the job tracker should not start 2 info servers
> -----------------------------------------------
>
> Key: HADOOP-2901
> URL: https://issues.apache.org/jira/browse/HADOOP-2901
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-2901.txt, patch-2901.txt, patch-2901.txt
>
>
> The job tracker should not start a second info server for job history.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.