Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 0.12.3
    • Fix Version/s: None
    • Component/s: util
    • Labels:
      None

      Description

      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.

      1. 1273.patch
        7 kB
        Tahir Hashmi
      2. hadoop-0.12.4-lib.tar.gz
        7.46 MB
        Tahir Hashmi

        Activity

        Hide
        Tahir Hashmi added a comment -

        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.

        Show
        Tahir Hashmi added a comment - 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.
        Hide
        Tahir Hashmi added a comment -

        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

        Show
        Tahir Hashmi added a comment - 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
        Hide
        Tahir Hashmi added a comment -

        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.

        Show
        Tahir Hashmi added a comment - 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.
        Hide
        Tahir Hashmi added a comment -

        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.

        Show
        Tahir Hashmi added a comment - 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.
        Hide
        Devaraj Das added a comment -

        Reopening this issue as jetty6.1.4 appears to have addressed some of the earlier problems

        Show
        Devaraj Das added a comment - Reopening this issue as jetty6.1.4 appears to have addressed some of the earlier problems

          People

          • Assignee:
            Devaraj Das
            Reporter:
            Owen O'Malley
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development