Hi Shimon, I spoke with a member of the Java client team and the timeout is set to 60 seconds. In the 2.0 version of the client this will be user-settable.
To make sure there's not a crash or other issue causing the long list keys, feel free to run "riak-debug" on nodes in your cluster and provide the generated archives. We can discuss that off-list. -- Luke Bakken CSE [email protected] On Wed, Dec 4, 2013 at 12:43 AM, Shimon Benattar <[email protected]> wrote: > Hi Luke, > We're using v1.4 > On Dec 3, 2013 6:19 PM, "Luke Bakken" <[email protected]> wrote: > >> Hi Shimon, >> >> What version of Riak and the Java client are you using? >> >> Thanks >> -- >> Luke Bakken >> CSE >> [email protected] >> >> >> On Thu, Nov 28, 2013 at 4:00 AM, Shimon Benattar <[email protected]>wrote: >> >>> Hi Riak users, >>> >>> >>> >>> Unfortunately for me I need to implement the get all keys method in our >>> system (I know it is not recommended) >>> >>> >>> >>> I am developing classes with the Java Api and using the streaming option >>> as following >>> >>> >>> >>> StreamingOperation<String> keys = riakBucket.keys(); >>> >>> while (keys.hasNext()) { >>> >>> final String next = keys.next(); >>> >>> out.write(next); >>> >>> out.newLine(); >>> >>> } >>> >>> riakBucket.keys().cancel(); >>> >>> >>> >>> My problem here is that for a simple class I inserted in Riak, after >>> ~4.7 million keys I am getting a timeout from Riak. >>> >>> Is there any way to configure the read operation timeout or to somehow >>> catch the timeout and continue to receive the next keys (Can I somehow bulk >>> read the keys)? >>> >>> >>> >>> Thanks, >>> >>> >>> >>> Shimon >>> >>> >>> >>> _______________________________________________ >>> 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
