Closed (fixed)
Project:
Apache Solr Search
Version:
5.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Reporter:
Created:
27 Aug 2009 at 13:44 UTC
Updated:
6 Nov 2009 at 11:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
robertdouglass commentedI don't really like this implementation for the general public. Is it proven that anyone needs this protection on normal servers, or just servers that have throttling? Also seems like an odd thing to make a configuration for (not that this patch has configuration), so I wouldn't want to go down that route.
Comment #2
pwolanin commentedLet's find a reasonable approach for this asap - it continues to be a problem.
I'm inclined to pt this patch in for the next RC if we don't have something better
Comment #3
pwolanin commentedHere's a mostly untested patch that groups Solr deletes by 500 at a time rather than sending one delete query per node.
This should give better performance in almost all cases, and be more compatible with a limits on update queries.
Comment #4
pwolanin commentedThat patch isn't really working and doesn't provide a useful count of nodes to be deleted. Here's a better one.
Comment #5
pwolanin commentedWith update to README
Comment #6
pwolanin commentedoops - missed README changes
Comment #7
pwolanin commentedminor tweak - stop sending updates on cron if one fails.
Comment #8
pwolanin commentedcommitted to 6.x-1.x
Comment #9
robertdouglass commentedAnd to DRUPAL-6--2
Comment #10
claudiu.cristeaThe patch for DRUPAL-5--2.
Comment #11
claudiu.cristeaFixed in #278744.