Hi Sean, I'm very sorry to say that you've found a featurebug. There was a fix put in here https://github.com/basho/riak_core/pull/332
But that means that the default timeout of 60 seconds is now honoured. In the past it was not. As far as I can see the 2i endpoint never accepted a timeout argument, and it still does not. The fix would be to add the timeout to the 2i API endpoints, and I'll do that straight away. In the meantime, I wonder if streaming the results would help, or if you'd still hit the overall timeout? Very sorry that you've run into this. Let me know if streaming helps, I've raised an issue here[1] if you want to track this bug Cheers Russell [1] https://github.com/basho/riak_kv/issues/610 On 26 Jul 2013, at 17:59, Sean McKibben <[email protected]> wrote: > I should have mentioned that I also tried: > curl -H "X-Riak-Timeout: 260000" > "http://127.0.0.1:8098/buckets/mybucket/index/test_bin/myval?timeout=260000"; > -i > but still receive the 500 error below exactly at the 60 second mark. Is this > a bug? > > Secondary to getting this working at all, is this documented anywhere? and > any way to set this timeout using the ruby riak client? > > Stream may well work, but I'm going to have to make a number of changes on > the client side to deal with the results. > > Sean > > On Jul 26, 2013, at 3:53 PM, Brian Roach <[email protected]> wrote: > >> 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 <[email protected]> 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 >>> [email protected] >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
