Hi Daniel,
Secondary index queries need at least 1/n_val primary partitions to be
available before it could run successfully and Riak would return
{error,insufficient_vnodes_available} while the required primary partitions
are coming up.
I would suggest defensive programming (retrying the 2i queries on error) as
a way to mitigate this.
Thanks,
Ciprian
On Wed, Mar 5, 2014 at 11:06 PM, Daniel Iwan <iwan.dan...@gmail.com> wrote:
> Thanks Ciprian
>
> We already have wait-for-service in our script and it looks like it's not a
> sufficient condition to satisfy secondary index query.
> How long application should wait before starting querying Riak using 2i?
> Should we do riak-admin transfers to make sure there are no vnode transfers
> happening?
>
> I'm trying to figure it out what {error,insufficient_vnodes_available}
> means
> in terms of 2i query.
> Does it mean not all primary partitions are up?
>
> Regards
> Daniel
>
>
>
> --
> View this message in context:
> http://riak-users.197444.n3.nabble.com/Cluster-start-and-2i-query-tp4030557p4030614.html
> Sent from the Riak Users mailing list archive at Nabble.com.
>
> _______________________________________________
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
