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 "Devaraj Das (JIRA)" <ji...@apache.org> on 2006/11/20 08:25:03 UTC
[jira] Created: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Roll back Jetty6.0.1 to Jetty5.1.4
----------------------------------
Key: HADOOP-736
URL: http://issues.apache.org/jira/browse/HADOOP-736
Project: Hadoop
Issue Type: Bug
Reporter: Devaraj Das
Assigned To: Devaraj Das
There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=all ]
Doug Cutting updated HADOOP-736:
--------------------------------
Status: Resolved (was: Patch Available)
Fix Version/s: 0.9.0
Resolution: Fixed
I just committed this. Thanks!
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Fix For: 0.9.0
>
> Attachments: jetty5.1.4.patch, jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=all ]
Devaraj Das updated HADOOP-736:
-------------------------------
Status: Patch Available (was: Open)
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Attachments: jetty5.1.4.patch, jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=comments#action_12451549 ]
Devaraj Das commented on HADOOP-736:
------------------------------------
If 'svn merge' is easier, I don't have any problems. Do I need to do anything on my part for this?
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Attachments: jetty5.1.4.patch, jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=comments#action_12451873 ]
Devaraj Das commented on HADOOP-736:
------------------------------------
Tried the bugfixed release but sort benchmark fails with it (I ran the benchmark twice and both the times it failed). A whole lot of reduces fail and finally the job is terminated. I have not analysed why but I think it is not safe to proceed with this version of Jetty (though they fixed one major bug yesterday but there might be more lurking around). My recommendation is to roll back.
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Attachments: jetty5.1.4.patch, jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=comments#action_12451687 ]
Owen O'Malley commented on HADOOP-736:
--------------------------------------
Actually, the Jetty developers found a probable fix: http://jira.codehaus.org/browse/JETTY-177#action_80644
Can we try the fix before rolling back?
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Attachments: jetty5.1.4.patch, jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=comments#action_12452017 ]
Doug Cutting commented on HADOOP-736:
-------------------------------------
Can someone verify whether 'svn merge -r 472202:472201 .' is sufficient? If so, it's considerably simpler.
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Attachments: jetty5.1.4.patch, jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=comments#action_12451446 ]
Doug Cutting commented on HADOOP-736:
-------------------------------------
Is this different than doing 'svn merge -r 472202:472201 .'? That's certainly a lot simpler, and the only conflict is CHANGES.txt...
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Attachments: jetty5.1.4.patch, jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=all ]
Devaraj Das updated HADOOP-736:
-------------------------------
Attachment: jetty5.1.4.patch
jetty5.1.4.patch is for updating the files StatusHttpServer.java and bin/hadoop.
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Attachments: jetty5.1.4.patch, jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=all ]
Devaraj Das updated HADOOP-736:
-------------------------------
Attachment: jettyfiles-5.1.4.tar.gz
The files/directories which should be removed from the current version of trunk/lib are:
1) jetty-6.0.1.jar
2) servlet-api-2.5-6.0.1.jar
3) jsp-2.0
4) jetty-util-6.0.1.jar
5) slf4j-jcl.jar
6) slf4j-jcl.LICENSE.txt
The attached tarball contains the trunk/lib files/directories that need to be there for Jetty5.1.4.
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Attachments: jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=comments#action_12451981 ]
Owen O'Malley commented on HADOOP-736:
--------------------------------------
I agree. 6.0 is clearly not ready for us.
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Attachments: jetty5.1.4.patch, jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-736) Roll back Jetty6.0.1 to Jetty5.1.4
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-736?page=comments#action_12452059 ]
Owen O'Malley commented on HADOOP-736:
--------------------------------------
I tried:
% svn merge -r 472202:472201 .
% svn merge -r 472349:472348 .
and the cluster works and runs jobs.
> Roll back Jetty6.0.1 to Jetty5.1.4
> ----------------------------------
>
> Key: HADOOP-736
> URL: http://issues.apache.org/jira/browse/HADOOP-736
> Project: Hadoop
> Issue Type: Bug
> Reporter: Devaraj Das
> Assigned To: Devaraj Das
> Attachments: jetty5.1.4.patch, jettyfiles-5.1.4.tar.gz
>
>
> There seems to be a problem with the current version of Jetty (6.0.1) in the case where we are using it for serving map outputs. It becomes very slow after serving a few outputs and doesn't recover from that state. Tried with the current release of Jetty - 6.1.0(pre1), but the problem seems to be there even with that release. So roll back to the previous Jetty version (5.1.4) seems to be right thing to do for now. This is the URL for the Jira issue on Jetty's performance issue:
> http://jira.codehaus.org/browse/JETTY-177
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira