hi ,
The current replication strategy in solr involves shell scripts . The
following are the drawbacks
* It does not work with windows
* Replication works as a separate piece not integrated with solr.
* Cannot control replication from solr admin/JMX
* Each operation requires manual telnet to the
The current scripts use rsync to minimize the amount of data actually
being copied.
I've had a brief look and found only 1 implementation which is GPL and
abandoned
http://sourceforge.net/projects/jarsync.
Personally I still think the size of the transfer is important (as for
most use cases
Hi Ian,
I assume that a sizeable amount of people do replication after an optimize
which causes almost the whole index to be transferred by rsync. We can do a
checksum based modification check on individual segment files and pull only
those from the master. Although that's not a true diff copy,
In the future, don't post the same idea in solr-user and solr-dev...
most people on solr-dev read solr-user and the cross posting splits
where discussion ends up.
On Apr 29, 2008, at 5:01 AM, Noble Paul നോബിള്
नोब्ळ् wrote:
hi ,
The current replication strategy in solr involves shell
We are not doing away with the current replication strategy. It's
just that
we're proposing an alternative.
I'm all for adding a replication strategy that works on windows and is
controlled/managed from the webapp. The existing hardlink rsync
methods may have better performance...
