lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pushkar Raste (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-9506) cache IndexFingerprint for each segment
Date Tue, 18 Oct 2016 15:10:59 GMT

    [ https://issues.apache.org/jira/browse/SOLR-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15585707#comment-15585707
] 

Pushkar Raste commented on SOLR-9506:
-------------------------------------

I think what Yonik is implying is that, if for some reason, replica does not apply delete
properly, index fingerprint would still checkout and that would be a problem.

Considering the issues with {{PeerSync}}, should add that option  {{recoverWithReplicationOnly}}
? For most of the setups I doubt if people would have hundreds of thousands of records in
updateLog in which which almost no one is using {{PeerSync}} anyway

> cache IndexFingerprint for each segment
> ---------------------------------------
>
>                 Key: SOLR-9506
>                 URL: https://issues.apache.org/jira/browse/SOLR-9506
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Noble Paul
>         Attachments: SOLR-9506.patch, SOLR-9506.patch, SOLR-9506_POC.patch
>
>
> The IndexFingerprint is cached per index searcher. it is quite useless during high throughput
indexing. If the fingerprint is cached per segment it will make it vastly more efficient to
compute the fingerprint



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message