Finally the issue was solved. I forgot to mention that I had a Logstash output connected and it's protocol <http://logstash.net/docs/1.4.2/outputs/elasticsearch#protocol> was set to 'node', meaning that logstash was part of my cluster. Once I set the protocol to 'transport',scrolling was perfect!!
Credit to my team-leader for guidance.... Thanks everyone for your help Yarden On Monday, November 10, 2014 7:06:52 PM UTC+2, Brian wrote: > > A while back, I wrote my own post-query response sorting so that I could > handle cases that Elasticsearch didn't. One case was sorting a scan query. > I used a Java TreeSet class and could also limit it to the top 'N' > (configurable) items. It is very, very quick, pretty much adding no > overhead to the existing scan logic. And it supports an arbitrarily > complex compound sort key, much like an SQL ORDERBY statement; it's very > easy to construct. > > Probably not useful for a normal user query, but it is very useful for an > ad-hoc query in which I wish to scan across an indeterminately large result > set but still sort the results. > > One of these days, it might make a good plug-in candidate. But I am not > sure how to integrate it with the scan API, so for now it's just part of > the Java client layer. > > Brian > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/44b5c8db-6c09-4527-b440-09d01bde3588%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
