We use BitTorrent for our deploys. It has reduced deployment time to 10%
for us also.
But I think this is where Solr vs ElasticSearch becomes interesting. Solr,
if I am correct, is Master-slave. That is one index is replicated but not
sharded. ES is sharded and replicated so individual replicas of individual
shards are much smaller than the entire index - well 1/shards times smaller.
Second, I think ES pushes changes to replicas as deltas already rather than
needing BitTorrent to hash and tell us what has changed.
So in the general usage pattern I don't think it'll help out that much. But
what about failure cases? Perhaps when you spin up a new node, that's when
a BitTorrent protocol could make you some savings in ES?
On Sat, Jan 28, 2012 at 2:07 AM, David Pilato email@example.com wrote:
That's a very interesting article.
They decrease the replication time from 60 mn to 6 mn using bittorrent
instead of http protocol !
That's really significant.
Le 28 janv. 2012 à 10:26, jprante firstname.lastname@example.org a écrit :
how about Bittorrent, could it be a feasible protocol for future
Elasticsearch replication between datacenters? Is the idea good or
bad? Pros and cons? Any comments welcome.
Just stumbled upon this post where Bittorrent protocol is used to
overcome solr index replication deficiencies (but within a datacenter