[
https://issues.apache.org/jira/browse/SOLR-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Steffensen closed SOLR-3428.
--------------------------------
Resolution: Fixed
None of the problems are present in latest code (looking at 5.1.0 release)
> SolrCmdDistributor flushAdds/flushDeletes problems
> --------------------------------------------------
>
> Key: SOLR-3428
> URL: https://issues.apache.org/jira/browse/SOLR-3428
> Project: Solr
> Issue Type: Bug
> Components: replication (java), SolrCloud, update
> Affects Versions: 4.0-ALPHA
> Reporter: Per Steffensen
> Assignee: Per Steffensen
> Labels: add, delete, replica, solrcloud, update
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> A few problems with SolrCmdDistributor.flushAdds/flushDeletes
> * If number of AddRequests/DeleteRequests in alist/dlist is below limit for a
> specific node the method returns immediately and doesnt flush for subsequent
> nodes
> * When returning immediately because there is below limit requests for a
> given node, then previous nodes that have already been flushed/submitted are
> not removed from adds/deletes maps (causing them to be flushed/submitted
> again the next time flushAdds/flushDeletes is executed)
> * The idea about just combining params does not work for SEEN_LEADER params
> (and probably others as well). Since SEEN_LEADER cannot be expressed (unlike
> commitWithin and overwrite) for individual operations in the request, you
> need to sent two separate submits. One containing requests with
> SEEN_LEADER=true and one with SEEN_LEADER=false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
