lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Updated] (SOLR-3428) SolrCmdDistributor flushAdds/flushDeletes problems
Date Thu, 02 Aug 2012 17:30:02 GMT


Mark Miller updated SOLR-3428:

    Fix Version/s: 5.0
> SolrCmdDistributor flushAdds/flushDeletes problems
> --------------------------------------------------
>                 Key: SOLR-3428
>                 URL:
>             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
>             Fix For: 4.0, 5.0
>   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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message