Hi Jeff, I suppose there should be slave configuration in solrconfig files which says to ping master to check for the version and get the modified files.
If replication is configured in slave you will see commands getting triggered and you could get some idea from there. Also you could paste that log if it not clear. Regards, Aman On Mon, Jun 4, 2018, 23:57 Jeff Courtade <courtadej...@gmail.com> wrote: > To be clear I deleted the actual index files out from under the running > master > > On Mon, Jun 4, 2018, 2:25 PM Jeff Courtade <courtadej...@gmail.com> wrote: > > > So are you saying it should have? > > > > It really acted like a normal function this happened on 5 different pairs > > in the same way. > > > > > > On Mon, Jun 4, 2018, 2:23 PM Aman Tandon <amantandon...@gmail.com> > wrote: > > > >> Could you please check the replication request commands in solr logs of > >> slave and see if it is complaining anything. > >> > >> On Mon, Jun 4, 2018, 23:45 Jeff Courtade <courtadej...@gmail.com> > wrote: > >> > >> > Hi, > >> > > >> > This I think is a very simple question. > >> > > >> > I have a solr 4.3 master slave setup. > >> > > >> > Simple replication. > >> > > >> > The master and slave were both running and synchronized up to date > >> > > >> > I went on the master and deleted the index files while solr was > running. > >> > solr created new empty index files and continued to serve requests. > >> > The slave did not delete its indexes and kept all of the old data in > >> place > >> > and continued to serve requests. > >> > > >> > This was strange as I would have thought the replica would have > >> replicated > >> > an empty index from the master. > >> > > >> > Does anyone have an explanation for this? I am fairly certain I just > am > >> not > >> > understanding something basic. > >> > > >> > J > >> > > >> > -- > >> > > >> > Jeff Courtade > >> > M: 240.507.6116 > >> > > >> > > -- > > > > Jeff Courtade > > M: 240.507.6116 > > > -- > > Jeff Courtade > M: 240.507.6116 >
