Typo? That's 60 seconds, but that's not especially interesting either way.

Yes, I was thinking about this too and I have changed it to 59 actually.

Do the actual segment's look identical after the polling?

Well no.

How  I am handling master slave.
How we do this use sym link for master and slave config. When converting
master to slave solrconfig.xml point to slave.xml and same for slave to
master. Than my script restart solr master and slave both. Script tells the
website which one is current master and website save current master url and
use it for searching.

What I have done when the problem started, I changed slave to master and
master to slave. Before this some thing went wrong on machine (could be the
reason of problem not really sure, checked system logs every thing was
fine) no idea what was wrong couldn't find it yet.

Ho did I fix it, I have to reinstall solr for slave, before re-installation
remove all directories related to solr. Not really ideal way to fix it. but
solved the problem and still curious what could cause that such problem?

Thanks,
Novin





On Thu, 11 Feb 2016 at 22:07 Erick Erickson <[email protected]> wrote:

> Typo? That's 60 seconds, but that's not especially interesting either way.
>
> Do the actual segment's look identical after the polling?
>
> On Thu, Feb 11, 2016 at 1:16 PM, Novin Novin <[email protected]> wrote:
> > Hi Erick,
> >
> > Below is master slave config:
> >
> > Master:
> > <requestHandler name="/replication" class="solr.Re1plicationHandler">
> >      <lst name="master">
> >         <str name="replicateAfter">commit</str>
> >         <str name="backupAfter">optimize</str>
> >     </lst>
> >     <int name="maxNumberOfBackups">2</int>
> >   </requestHandler>
> >
> > Slave:
> > <requestHandler name="/replication" class="solr.ReplicationHandler" >
> >     <lst name="slave">
> >       <!-- <str
> > name="masterUrl">http://remote_host:port
> /solr/core_name/replication</str>
> > -->
> >       <str name="masterUrl">http://master:8983/solr/big_core/replication
> > </str>
> >       <str name="pollInterval">00:00:60</str>
> >       <str name="httpBasicAuthUser">username</str>
> >       <str name="httpBasicAuthPassword">password</str>
> >      </lst>
> >   </requestHandler>
> >
> >
> > Do you mean the Solr is restarting every minute or the polling
> > interval is 60 seconds?
> >
> > I meant polling is 60 minutes
> >
> > I didn't not see any suspicious in logs , and I'm not optimizing any
> thing
> > with commit.
> >
> > Thanks
> > Novin
> >
> > On Thu, 11 Feb 2016 at 18:02 Erick Erickson <[email protected]>
> wrote:
> >
> >> What is your replication configuration in solrconfig.xml on both
> >> master and slave?
> >>
> >> bq:  big core is doing full sync every time wherever it start (every
> >> minute).
> >>
> >> Do you mean the Solr is restarting every minute or the polling
> >> interval is 60 seconds?
> >>
> >> The Solr logs should tell you something about what's going on there.
> >> Also, if you are for
> >> some reason optimizing the index that'll cause a full replication.
> >>
> >> Best,
> >> Erick
> >>
> >> On Thu, Feb 11, 2016 at 8:41 AM, Novin Novin <[email protected]>
> wrote:
> >> > Hi Guys,
> >> >
> >> > I'm having a problem with master slave syncing.
> >> >
> >> > So I have two cores one is small core (just keep data use frequently
> for
> >> > fast results) and another is big core (for rare query and for search
> in
> >> > every thing). both core has same solrconfig file. But small core
> >> > replication is fine, other than this big core is doing full sync every
> >> time
> >> > wherever it start (every minute).
> >> >
> >> > I found this
> >> >
> >>
> http://stackoverflow.com/questions/6435652/solr-replication-keeps-downloading-entire-index-from-master
> >> >
> >> > But not really usefull.
> >> >
> >> > Solr verion 5.2.0
> >> > Small core has doc 10 mil. size around 10 to 15 GB.
> >> > Big core has doc greater than 100 mil. size around 25 to 35 GB.
> >> >
> >> > How can I stop full sync.
> >> >
> >> > Thanks
> >> > Novin
> >>
>

Reply via email to