The information is not sufficient to say something. You can refer to solr log to find the reason of log replay. You can also check if the index is as per expectation. E.g Number of document indexed.
Regards, Modassar On Tue, Nov 3, 2015 at 11:11 AM, Midas A <test.mi...@gmail.com> wrote: > Thanks Modassar for replying , > > could u please elaborate ..what wuld have happened when we were getting > this kind of warning ds > > Regards, > Abhishek Tiwari > > On Mon, Nov 2, 2015 at 6:00 PM, Modassar Ather <modather1...@gmail.com> > wrote: > > > Normally tlog is replayed in case if solr server crashes for some reason > > and when restarted it tries to recover from the crash gracefully. > > You can look into following documentation which explains about > transaction > > logs and related stuff of Solr. > > > > > > > http://lucidworks.com/blog/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/ > > > > regards, > > Modassar > > > > On Mon, Nov 2, 2015 at 12:22 PM, Midas A <test.mi...@gmail.com> wrote: > > > > > Please explain following warning > > > > > > Starting log replay > > > tlog{file=/mnt/vol1/path/data/tlog/tlog.0000000000000060544 refcount=2} > > > active=false starting pos=0 > > > > > > Is there any harm with this error ? > > > > > >
