On Mon, Sep 24, 2012 at 1:27 PM, Alfonso De Gregorio <[email protected]> wrote: > Hi All, > > Does the Search indexing precommit hook adversely affects the maximum > number of buckets a Riak cluster can handle? > > More specifically: as long as we don't change their properties, > buckets are namespaces for our keys and, theoretically, there is no > limit to their number [1,2]. At the same time, Search indexes Riak KV > objects as they're written using a precommit hook -- a bucket property > [3]. I was wondering if this specific change in bucket properties may > force Riak to gossip more data around the cluster and, in turn, > degrade the performance. I'm assuming a Bitcask backend. So, how many > buckets a Riak cluster can handle while using Riak Search?
>From a closer look at the architecture, I understand now that Riak Search partitions the index entries by term across the cluster. So, I guess some queries are slower than others, due to the increased traffic between search nodes. Therefore I expect also the maximum number of buckets to be affected. Does anybody can provide me a rough estimate of how many bucket Riak Search can handle, please? Knowing the order of magnitude for this quantity would get me one step closer to completing the preliminary design for a project, where I would be more than happy to have Riak. Thank you. Ciao, alfonso > Thank you for any insight on the above and kudos to all people at > Basho for all the work done on Riak. > > Ciao, > alfonso > > [1] http://wiki.basho.com/Concepts.html > [2] > http://lists.basho.com/pipermail/riak-users_lists.basho.com/2010-December/002569.html > [3] http://wiki.basho.com/Riak-Search.html -- Alfonso De Gregorio http://Plaintext.crypto.lo.gy _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
