lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akshay K. Ukey (JIRA)" <>
Subject [jira] Updated: (SOLR-829) replication Compression
Date Thu, 20 Nov 2008 18:12:44 GMT


Akshay K. Ukey updated SOLR-829:

    Attachment: solr-829.patch

Patch with additional configuration in replicationhandler as suggested by Noble.
<lst name="slave">
  <!-- values can be internal|external. --> 
  <str name="compression">internal</str>

If internal compression is used InflaterInputStream and DeflaterOutputStream Java apis are
used for data transfer from master to slaves. 

If external compression is used Accept-Encoding header value is set to "gzip,deflate" before
making request to the master. And the container has to be configured with appropriate setting.
E.g. In case of Tomcat, following settings are to be done in the Connector section to use
Tomcat's compression mechanism:
<Connector .... compression=on 

> replication Compression
> -----------------------
>                 Key: SOLR-829
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: replication (java)
>            Reporter: Simon Collins
>            Assignee: Shalin Shekhar Mangar
>         Attachments: email discussion.txt, solr-829.patch, solr-829.patch, solr-829.patch
> From a discussion on the mailing list solr-user, it would be useful to have an option
to compress the files sent between servers for replication purposes.
> Files sent across between indexes can be compressed by a large margin allowing for easier
replication between sites.
> ...Noted by Noble Paul 
> we will use a gzip on both ends of the pipe . On the slave side you can say <str name="zip">true<str>
as an extra option to compress and send data from server 
> Other thoughts on issue: 
> Do keep in mind that compression is a CPU intensive process so it is a trade off between
CPU utilization and network bandwidth.  I have see cases where compressing the data before
a network transfer ended up being slower than without compression because the cost of compression
and un-compression was more than the gain in network transfer.
> Why invent something when compression is standard in HTTP? --wunder

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message