You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Ravi Prakash (JIRA)" <ji...@apache.org> on 2015/01/29 03:06:35 UTC

[jira] [Updated] (HADOOP-11516) Enable HTTP compression on all hadoop UIs

     [ https://issues.apache.org/jira/browse/HADOOP-11516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ravi Prakash updated HADOOP-11516:
----------------------------------
    Attachment: HADOOP-11516.01.patch

Ideally this would be all that is required to turn on compression.

HOWEVER :( as reported by Bobby here : https://jira.codehaus.org/browse/JETTY-1518 , Jersey had a bug : https://java.net/jira/browse/JERSEY-1207 .

This is claimed to be fixed in Jersey 2.x . Which makes me wonder if we have any plans to move to it.

> Enable HTTP compression on all hadoop UIs
> -----------------------------------------
>
>                 Key: HADOOP-11516
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11516
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Ravi Prakash
>         Attachments: HADOOP-11516.01.patch
>
>
> Some of our UI pages (e.g. # of jobs, # of task attempts, logs) are extremely big. It would drastically improve their load times if we used HTTP compression.
> There exists a GzipFilter for jetty that can be added so that if the browser includes "Accept-Encoding: gzip, deflate" in the request header, the server will respond with the resource compressed and a response header "Content-Encoding: gzip" (or deflate). http://www.eclipse.org/jetty/documentation/current/gzip-filter.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)