[
https://issues.apache.org/jira/browse/SOLR-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15520747#comment-15520747
]
Pushkar Raste edited comment on SOLR-9310 at 9/25/16 12:51 PM:
---------------------------------------------------------------
I went through logs at
https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-MacOSX/429/consoleFull
If PeerSync was unsuccessful I would expect to see a line like
{{o.a.s.u.PeerSync Fingerprint comparison: -1}}
However, I don't see such line. I could think of two scenarios that could break
the test
* data directory could get deleted while a node is brought down, since data
directory is created in {{temp}}. Upon restart replica would have no frame of
reference and will have to fall back on replication.
* we need a better check than relying number of requests made to
{{ReplicationHandler}}
was (Author: praste):
I went through logs in the failed test email notification but those are
truncated. Where can I look at the entire build.log for the test.
Only thing I could think of at this point is data directory could get deleted
while a node is brought down, since data directory is created in {{temp}}. Upon
restart replica would have no frame of reference and will have to fall back on
replication.
> PeerSync fails on a node restart due to IndexFingerPrint mismatch
> -----------------------------------------------------------------
>
> Key: SOLR-9310
> URL: https://issues.apache.org/jira/browse/SOLR-9310
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Pushkar Raste
> Assignee: Noble Paul
> Fix For: 5.5.3, 6.3, trunk
>
> Attachments: PeerSync_3Node_Setup.jpg, PeerSync_Experiment.patch,
> SOLR-9310.patch, SOLR-9310.patch, SOLR-9310.patch, SOLR-9310.patch,
> SOLR-9310.patch, SOLR-9310.patch, SOLR-9310_3ReplicaTest.patch,
> SOLR-9310_5x.patch, SOLR-9310_final.patch
>
>
> I found that Peer Sync fails if a node restarts and documents were indexed
> while node was down. IndexFingerPrint check fails after recovering node
> applies updates.
> This happens only when node restarts and not if node just misses updates due
> reason other than it being down.
> Please check attached patch for the test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]