I think multiple queries does the trick. Here's an evil scenario that can produce it if done a couple times.
1) Run a cruelly long query (e.g. * ) 2) Run, several non-trivial, but not evil queries over and over. 3) One of the non-trivial queries fails with the "out of sequence" error. 4) Then, Mr. Cruel Query fails with a "TTransportException: j.n.SocketTimeoutException: Read Timed Out" I think the corpus has to be reasonably large for it to be slow enough to occur. Thanks, --tim On Tue, Dec 17, 2013 at 3:48 PM, Aaron McCurry <[email protected]> wrote: > So it's during a query call (+ some other call)? > > > On Tue, Dec 17, 2013 at 3:38 PM, Tim Williams <[email protected]> wrote: > >> Appears to be between controller and shards, with the exception on the >> controller side... >> >> BlurResultIterableClient.performSearch(BlurResultIterableClient.java:77) >> ... >> BlurControllerServer.call(BlurControllerServer.java:396) >> ... >> >> That's where it heads into generated code territory. The whole trace >> isn't easily pastable for me so let me know if more context is >> necessary... >> >> Thanks, >> --tim >> >> On Tue, Dec 17, 2013 at 3:08 PM, Aaron McCurry <[email protected]> wrote: >> > Tim you are right this only occurs when a thrift client has more then one >> > thread using it. Can you isolate where the error is occurring? Meaning >> is >> > it between the controller and shard or between your client and the >> > controller? Because if it's between your client and the controller it's >> > likely something going on in your application logic. If not, then >> there's >> > a bug somewhere in the client use/reuse. >> > >> > Aaron >> > >> > >> > On Tue, Dec 17, 2013 at 2:54 PM, Garrett Barton < >> [email protected]>wrote: >> > >> >> Used to see that with Blur when I did not set a id on the query. Don't >> >> know if Aaron sets some unique identifier on calls like schema though... >> >> >> >> >> >> On Tue, Dec 17, 2013 at 2:46 PM, Tim Williams <[email protected]> >> >> wrote: >> >> >> >> > I'm periodically seeing this on various calls - both query and >> >> > seemingly harmless ones (e.g. schema). Google hints that it happens >> >> > when the client is used across threads. Anyone see it before? Know >> >> > how to solve it? >> >> > >> >> > Thanks, >> >> > --tim >> >> > >> >> >>
