Hi Erick
> You're probably on your own here. I'd be surprised if people were
willing to work on code of that vintage.
Yes, this is not a vintage wine!
I just hoped someone would say, "ah, we had this issue before and..." :-)
I think best is to just upgrade like you suggested.
Thanks for your t
Oh, 1.4.1. You're probably on your own here. I'd be surprised if
people were willing to work on code of that vintage. Are
you sure you can't upgrade at least to 3.6?
Best
Erick
On Sun, Oct 28, 2012 at 12:43 PM, Eric Grobler
wrote:
> Hi Erick,
>
> It is Solr 1.41 (a Drupal installation) running o
Hi Erick,
It is Solr 1.41 (a Drupal installation) running on Jetty.
How can one get a stack trace? (there is no exception/error)
Could it be that solr does something like this?
start delete job
cannot find bogus id to delete
does some reindex or optimization anyway regardless which takes 80
That is very weird. What version of Solr are you using, and is there
any way you could get a stack trace when this is happening?
Best
Erick
On Sun, Oct 28, 2012 at 6:22 AM, Eric Grobler wrote:
> Hi
>
> I am a bit confused why the server sometimes takes 80 seconds to respond
> when I specify an i
Hi
I am a bit confused why the server sometimes takes 80 seconds to respond
when I specify an id to delete than does not even exist in the index.
If I loop this query and send a bogus id to delete every minute.
03:27:38 125 ms bogusidthatdoesnotexist commit
03:28:38 125 ms bogusidthatdoesno
