Re: Multiple collections vs multiple shards for multitenancy

2017-05-07 Thread Chris Troullis
Thanks for the great advice Erick. I will experiment with your suggestions and see how it goes! Chris On Sun, May 7, 2017 at 12:34 AM, Erick Erickson wrote: > Well, you've been doing your homework ;). > > bq: I am a little confused on this statement you made: > > > Plus you can't commit > > ind

Re: Multiple collections vs multiple shards for multitenancy

2017-05-06 Thread Erick Erickson
Well, you've been doing your homework ;). bq: I am a little confused on this statement you made: > Plus you can't commit > individually, a commit on one will _still_ commit on all so you're > right back where you started. Never mind. autocommit kicks off on a per replica basis. IOW, when a new d

Re: Multiple collections vs multiple shards for multitenancy

2017-05-06 Thread Chris Troullis
Hi Erick, Thanks for the reply, I really appreciate it. To answer your questions, we have a little over 300 tenants, and a couple of different collections, the largest of which has ~11 million documents (so not terribly large). We are currently running standard Solr with simple master/slave repli

Re: Multiple collections vs multiple shards for multitenancy

2017-05-06 Thread Erick Erickson
Well, it's not either/or. And you haven't said how many tenants we're talking about here. Solr startup times for a single _instance_ of Solr when there are thousands of collections can be slow. But note what I am talking about here: A single Solr on a single node where there are hundreds and hundr