http://wiki.apache.org/solr/SolrReplication#head-b77f4610e9b2f38433fdffc7f07cc9789ecabe72
On Sun, Jan 18, 2009 at 10:53 PM, Shalin Shekhar Mangar
wrote:
> On Sun, Jan 18, 2009 at 9:51 PM, Yonik Seeley wrote:
>
>>
>> I've not looked into the file replication part much (as opposed to the
>> inde
On Sun, Jan 18, 2009 at 9:51 PM, Yonik Seeley wrote:
>
> I've not looked into the file replication part much (as opposed to the
> index replication).
> Master and Slave solrconfig.xml will most likely need to be different
> though... is that addressed somehow?
>
Yes. You can provide an alias to
On Fri, Jan 16, 2009 at 3:33 AM, Noble Paul നോബിള് नोब्ळ्
wrote:
> inbuilt replication allows schema/conf replication which makes a lot
> of these unnecessary.
> All disable enable stuff are exposed as http commands
I've not looked into the file replication part much (as opposed to the
index re
On Fri, Jan 16, 2009 at 3:37 AM, Chris Hostetter
wrote:
>
> : I would like to know the advantages of moving from:
> : a master-slave system using CollectionDistribution with all their .sh
> : scripts
> : http://wiki.apache.org/solr/CollectionDistribution
> : to:
> : use SolrReplication and his sol
: I would like to know the advantages of moving from:
: a master-slave system using CollectionDistribution with all their .sh
: scripts
: http://wiki.apache.org/solr/CollectionDistribution
: to:
: use SolrReplication and his solrconfig.xml configuration.
: http://wiki.apache.org/solr/SolrReplicati
The problem with that approach is that unlike databases, a commit is an
expensive operation in Lucene right now. It is not very practical to commit
per document, therefore log replication offers very little.
On Tue, Jan 6, 2009 at 12:07 AM, Jacob Singh wrote:
> Has there been a discussion anywhe
Has there been a discussion anywhere about a "binary log" style
replications scheme (ala mysql?) Wherein, every write request goes to
the master, and the the slaves read in a queue of the requests and
update themselves one record at a time instead of wholesale? Or is
this just not worth the devel
The default IndexDeletionPolicy just keeps the last commit only
(KeepOnlyLastCommitDeletionPolicy) .Files belonging to older commits
are removed. If the files are needed longer for replication, they are
leased . The lease is extended 10 secs at a time. Once all the slaves
have copied the lease is n
Noble Paul ??? ?? wrote:
* SolrReplication does not create snapshots . So you have less cleanup
to do. The script based replication results is more disk space
consumption (especially if you do frequent commits)
Doesn't SolrReplication effectively take a snapshot by using a custom
Inde
>> similar except for the RAM, are the advantages about that?
>>
>> Thanks in advance!!
>> --
>> View this message in context:
>> http://www.nabble.com/collectionDistribution-vs-SolrReplication-tp21269112p21269112.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>
--
--Noble Paul
?
> Does SolrReplication do warming aswell?
>
> Checking performance numbers is solrReplication wiki page things seem to be
> similar except for the RAM, are the advantages about that?
>
> Thanks in advance!!
> --
> View this message in context:
> http://www.nabble.com/coll
://www.nabble.com/collectionDistribution-vs-SolrReplication-tp21269112p21269112.html
Sent from the Solr - User mailing list archive at Nabble.com.
12 matches
Mail list logo
