limit of bucket/solr indexes
13vitamins at gmail.com
Fri Jan 15 13:12:04 EST 2016
I didn't see anybody answering your question, so I'll try my best to answer
The practical number of Solr indices in Riak KV is pretty low. I won't
recommend working with more than a few. We hit severe performance problems
at around a few tens of Solr indexes. So it looks like if Solr search is
absolutely a must for you, you'll have to share an index among the teams
and filter out search results (by team).
Regarding buckets, there can be a lot. That said, I would suggest utilizing
bucket types to get better performance. When the properties of a bucket are
derived from a bucket type, it's mostly the bucket type that needs to be
replicated across Riak nodes, as opposed to replicating the properties of
every individual bucket (
Am I right assuming that the nature (or structure if you will) of data will
be the same for different teams? If this is the case, it may make sense to
configure bucket properties at the bucket-type level, including any
associated Solr indexes.
For example, you may have the following structure:
bucket type: team_members
properties: w = quorum, r = quorum, search_index = team_members
And then "child" buckets:
and so on
If you decide to use this approach, let me know how it works for you.
On Wed, Nov 18, 2015 at 12:02 PM, Alexander Popov <mogadanez at gmail.com>
> 1. does Riak have restrictions on bucket numbers?
> 2. same for SOLR indexes?
> Interesting not theoretical, but practical limits when it start works bad.
> Use case: we want split users bucket to bucket-per-team model,
> this bucket have also solr index on top. Can it work for 1000 teams? 10k?
> riak-users mailing list
> riak-users at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users