Rebooting did the trick. Two things to mention: 1) The index was
relatively large at one point (1m+ documents); 2) I ran a number of
delete by queries to clear out stuff along the way. I did -XDELETE the
entire index and restart, and still go the bad behavior. Only
Hard to say what caused it, but problem solved for now.
On Sep 23, 5:25 pm, searchersteve steve...@gmail.com wrote:
I'm afraid I can't think of how to recreate it. I could show you my
mapping and the data that I am indexing. But as I say, it was all
working fine until recently. And if there were an error in the mapping
or API syntax, then ES should tell me right away, right?
I will spend some time on it and let you know what I find. First thing
I plan to try is reboot ES.
On Sep 23, 4:54 pm, Shay Banon kim...@gmail.com wrote:
Strange, it should not hang... . Is there a simple way to recreate it?
On Fri, Sep 23, 2011 at 10:13 PM, Steve Suo steve...@gmail.com wrote:
I have process that routinely submits content to ElasticSearch via
cURL and the PUT method:
curl -XPUT 'http://localhost:9200/twitter/tweets/_bulk'-d'XYZ INDEX
This has worked fine for several months. Recently, certain requests
have caused cURL to run indefinitely. When I submit a test request at
the command line, my cURL client's progress bar tells me that it's
transferred 6000 (bytes?). The progress bar stops at that number, but
the "Total time" indicator keeps going and going.
Thinking there might be a problem with my index (I've submitted a
number of DELETE BY queries recently), I deleted the entire index and
started over. But the same thing keeps happening.
Has anyone else had this problem?