Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates
 209.85.214.44 as permitted sender)
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: 
 <CAGpTDNecKcG=K0y+3uQ8A4i1a30kS=-gAv6JTBxRQ7N9Ce2Ueg@mail.gmail.com>
References: 
 <CA+r7YvkGGzKG7PQ+sN8T-r1ZJA=-+oL1zFud9PA9OG8suEzL_w@mail.gmail.com>
	<CAOtJ30rrC+_X380qEme3u7XdkeabqgNfkw9G5=9KtX_oHOPuLw@mail.gmail.com>
	<CA+r7YvkM+hJmROCNcHEGvVDpyQ=YArzT_yaURYg9GCuynrQdUA@mail.gmail.com>
	<CAGpTDNecKcG=K0y+3uQ8A4i1a30kS=-gAv6JTBxRQ7N9Ce2Ueg@mail.gmail.com>
Date: Wed, 5 Jun 2013 01:34:10 +0200
Message-ID: 
 <CADcMMgFKBvF-d09SfPi3tQfPSvr25MFEZQgLpQUS=Vq4Q8VAuw@mail.gmail.com>
Subject: Re: RPC Replication Compression
From: Stack <stack@duboce.net>
To: Hbase-User <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11c350a6aca50804de5c84cd

--001a11c350a6aca50804de5c84cd
Content-Type: text/plain; charset=UTF-8

On Tue, Jun 4, 2013 at 6:48 PM, Jean-Daniel Cryans <jdcryans@apache.org>wrote:

> Replication doesn't need to know about compression at the RPC level so
> it won't refer to it and as far as I can tell you need to set
> compression only on the master cluster and the slave will figure it
> out.
>
> Looking at the code tho, I'm not sure it works the same way it used to
> work before everything went protobuf. I would give 2 internets to
> whoever tests 0.95.1 with RPC compression turned on and compares
> results with non-compressed RPC. See
> http://hbase.apache.org/book.html#rpc.configs


What are you looking for JD?  Faster replication or just less network used?

Looks like we have not had the ability to do compressed rpc before (We
almost did,  the original rpc compression attempt almost got committed to
trunk -- see HBASE-5355 and the referenced follow-on issue -- but was put
aside after the pb stuff went in).

St.Ack

--001a11c350a6aca50804de5c84cd--