Well, a full import is going to re-import everything in the database, and the
presumption is that each every document would be replaced (because
presumably you're is the same). So every document
will be deleted and re-added. So essentially you'll get a completely
new index every time.
In 3.6 are
thank u for replying very much .
in fact ,we make a process for this problem , we found when master building
index, it will clean self index when building index . so slave every minute
to sync index, destroy self index folder.
by the way : we building index using
dataimport0?command=full-impor
Are you mixing SolrCloud and old-style master/slave?
There was a bug a while ago (search the JIRA) where
replication was copying the entire index unnecessarily,
but I think that was fixed by 4.3.
Best
Erick
On Tue, Jul 23, 2013 at 6:33 AM, xiaoqi wrote:
>
> hi,all
>
> i have two solr ,one is ma
hi,all
i have two solr ,one is master , one is replication , before i use them
under 3.5 version . it works fine .
when i upgrade to 4.3version , i found when replication solr copying index
from master , it will clean current index and copy new version to self
folder . slave can't search durin
