2i timeouts in 1.4

Brian Roach roach at basho.com
Fri Jul 26 17:53:04 EDT 2013


Sean -

The timeout isn't via a header, it's a query param -> &timeout=xxxx

You can also use stream=true to stream the results.

- Roach

Sent from my iPhone

On Jul 26, 2013, at 3:43 PM, Sean McKibben <graphex at graphex.com> wrote:

> We just upgraded to 1.4 and are having a big problem with some of our larger 2i queries. We have a few key queries that takes longer than 60 seconds (usually about 110 seconds) to execute, but after going to 1.4 we can't seem to get around a 60 second timeout.
> 
> I've tried:
> curl -H "X-Riak-Timeout: 260000" "http://127.0.0.1:8098/buckets/mybucket/index/test_bin/myval?x-riak-timeout=260000" -i
> 
> But I always get
> HTTP/1.1 500 Internal Server Error
> Vary: Accept-Encoding
> Server: MochiWeb/1.1 WebMachine/1.10.0 (never breaks eye contact)
> Date: Fri, 26 Jul 2013 21:41:28 GMT
> Content-Type: text/html
> Content-Length: 265
> Connection: close
> 
> <html><head><title>500 Internal Server Error</title></head><body><h1>Internal Server Error</h1>The server encountered an error while processing this request:<br><pre>{error,{error,timeout}}</pre><P><HR><ADDRESS>mochiweb+webmachine web server</ADDRESS></body></html>
> 
> Right at the 60 second mark. What can I set to give my secondary index queries more time??
> 
> This is causing major problems for us :(
> 
> Sean
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20130726/09d80af3/attachment.html>


More information about the riak-users mailing list