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 2007/04/20 00:22:15 UTC
[jira] Created: (HADOOP-1273) Upgrade Jetty to 6.x
Upgrade Jetty to 6.x
--------------------
Key: HADOOP-1273
URL: https://issues.apache.org/jira/browse/HADOOP-1273
Project: Hadoop
Issue Type: Improvement
Components: util
Affects Versions: 0.12.3
Reporter: Owen O'Malley
Assigned To: Tahir Hashmi
We should try again to upgrade to Jetty 6 (previous attempt was HADOOP-565 and HADOOP-736) because it should substantially help the cpu usage on the TaskTracker. See http://www.infoq.com/news/jetty-6-release for a discussion of the improvements to Jetty 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-1273) Upgrade Jetty to 6.x
Posted by "Tahir Hashmi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tahir Hashmi resolved HADOOP-1273.
----------------------------------
Resolution: Won't Fix
Since Jetty 6 still doesn't appear to be stable enough, we've decided to investigate Grizzly for the same. See HADOOP-1432 for details.
> Upgrade Jetty to 6.x
> --------------------
>
> Key: HADOOP-1273
> URL: https://issues.apache.org/jira/browse/HADOOP-1273
> Project: Hadoop
> Issue Type: Improvement
> Components: util
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Tahir Hashmi
> Attachments: 1273.patch, hadoop-0.12.4-lib.tar.gz
>
>
> We should try again to upgrade to Jetty 6 (previous attempt was HADOOP-565 and HADOOP-736) because it should substantially help the cpu usage on the TaskTracker. See http://www.infoq.com/news/jetty-6-release for a discussion of the improvements to Jetty 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1273) Upgrade Jetty to 6.x
Posted by "Tahir Hashmi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498642 ]
Tahir Hashmi commented on HADOOP-1273:
--------------------------------------
As per http://jira.codehaus.org/browse/JETTY-345#action_96904, the bug that causes EofExceptions to occur has been identifiend in a 6.1.4 release candidate. However, the port retrieval issue might still remain. I tried doing webServer.join() a few days back and it had disastrous consequences. Not sure why.
Since deploying Jetty 6 at this stage requires using an RC, and we're not sure if that's going to solve all of the problems, it might be reasonable to abandon the upgrade for now.
> Upgrade Jetty to 6.x
> --------------------
>
> Key: HADOOP-1273
> URL: https://issues.apache.org/jira/browse/HADOOP-1273
> Project: Hadoop
> Issue Type: Improvement
> Components: util
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Tahir Hashmi
> Attachments: 1273.patch, hadoop-0.12.4-lib.tar.gz
>
>
> We should try again to upgrade to Jetty 6 (previous attempt was HADOOP-565 and HADOOP-736) because it should substantially help the cpu usage on the TaskTracker. See http://www.infoq.com/news/jetty-6-release for a discussion of the improvements to Jetty 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1273) Upgrade Jetty to 6.x
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-1273:
--------------------------------
Assignee: Devaraj Das (was: Tahir Hashmi)
Reopening this issue as jetty6.1.4 appears to have addressed some of the earlier problems
> Upgrade Jetty to 6.x
> --------------------
>
> Key: HADOOP-1273
> URL: https://issues.apache.org/jira/browse/HADOOP-1273
> Project: Hadoop
> Issue Type: Improvement
> Components: util
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assignee: Devaraj Das
> Attachments: 1273.patch, hadoop-0.12.4-lib.tar.gz
>
>
> We should try again to upgrade to Jetty 6 (previous attempt was HADOOP-565 and HADOOP-736) because it should substantially help the cpu usage on the TaskTracker. See http://www.infoq.com/news/jetty-6-release for a discussion of the improvements to Jetty 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1273) Upgrade Jetty to 6.x
Posted by "Tahir Hashmi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tahir Hashmi updated HADOOP-1273:
---------------------------------
Attachment: hadoop-0.12.4-lib.tar.gz
> Upgrade Jetty to 6.x
> --------------------
>
> Key: HADOOP-1273
> URL: https://issues.apache.org/jira/browse/HADOOP-1273
> Project: Hadoop
> Issue Type: Improvement
> Components: util
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Tahir Hashmi
> Attachments: hadoop-0.12.4-lib.tar.gz
>
>
> We should try again to upgrade to Jetty 6 (previous attempt was HADOOP-565 and HADOOP-736) because it should substantially help the cpu usage on the TaskTracker. See http://www.infoq.com/news/jetty-6-release for a discussion of the improvements to Jetty 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1273) Upgrade Jetty to 6.x
Posted by "Tahir Hashmi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tahir Hashmi updated HADOOP-1273:
---------------------------------
Attachment: 1273.patch
Attaching the patch that's been applied to the current source and a tarball of the lib directory. JT and TaskTrackers info webservers start now but they give 404 for everything. Needs further investigation.
> Upgrade Jetty to 6.x
> --------------------
>
> Key: HADOOP-1273
> URL: https://issues.apache.org/jira/browse/HADOOP-1273
> Project: Hadoop
> Issue Type: Improvement
> Components: util
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Tahir Hashmi
> Attachments: 1273.patch, hadoop-0.12.4-lib.tar.gz
>
>
> We should try again to upgrade to Jetty 6 (previous attempt was HADOOP-565 and HADOOP-736) because it should substantially help the cpu usage on the TaskTracker. See http://www.infoq.com/news/jetty-6-release for a discussion of the improvements to Jetty 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1273) Upgrade Jetty to 6.x
Posted by "Tahir Hashmi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498265 ]
Tahir Hashmi commented on HADOOP-1273:
--------------------------------------
Status update: After more than a week of pecking at it, we managed to get a few sort-350 and sort-500 runs that performed as well as, but no better than, the jetty-5 codebase. Unfortunately, as of now we've hit some deep waters. The problems are mentioned at the following issue on Jetty: http://jira.codehaus.org/browse/JETTY-345
> Upgrade Jetty to 6.x
> --------------------
>
> Key: HADOOP-1273
> URL: https://issues.apache.org/jira/browse/HADOOP-1273
> Project: Hadoop
> Issue Type: Improvement
> Components: util
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Tahir Hashmi
> Attachments: 1273.patch, hadoop-0.12.4-lib.tar.gz
>
>
> We should try again to upgrade to Jetty 6 (previous attempt was HADOOP-565 and HADOOP-736) because it should substantially help the cpu usage on the TaskTracker. See http://www.infoq.com/news/jetty-6-release for a discussion of the improvements to Jetty 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.