This is not a problem. The message is logged during replication where it tries to find files that are mis-matched between leader and replica to determine whether a full or a partial replication is to be performed. If you actually get an exception in the logs saying CorruptIndexException then it is more serious and should be reported to us in a Jira or the mailing list.
On Thu, Apr 9, 2015 at 12:44 PM, Aman Tandon <amantandon...@gmail.com> wrote: > Hi, > > I am getting this type of error while indexing on solr cloud. Could > somebody help, I have no knowledge what it is. > > > WARN - 2015-04-09 07:11:27.705; org.apache.solr.handler.SnapPuller; File > _p_Lucene50_0.tip did not match. expected checksum is 1515849197 and actual > is checksum 1522458868. expected length is 1188 and actual length is 2409 > WARN - 2015-04-09 07:11:27.709; org.apache.solr.handler.SnapPuller; File _ > p.si did not match. expected checksum is 2426498564 and actual is checksum > 4157813087. expected length is 396 and actual length is 394 > > > With Regards > Aman Tandon > -- Regards, Shalin Shekhar Mangar.
