Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of aurelien.mazoyer@francelabs.com
 designates 46.105.76.65 as permitted sender)
Message-ID: <53CFB0C0.20809@francelabs.com>
Date: Wed, 23 Jul 2014 14:55:28 +0200
From: =?ISO-8859-1?Q?Aur=E9lien_MAZOYER?=
 <aurelien.mazoyer@francelabs.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: solr-user@lucene.apache.org
Subject: Passivate core in Solr Cloud
Content-Type: multipart/alternative;
 boundary="------------000701010100030303000503"

--------------000701010100030303000503
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

We want to setup a Solr Cloud cluster in order to handle a high volume 
of documents with a multi-tenant architecture. The problem is that an 
application-level isolation for a tenant (using a mutual index with a 
field "customer") is not enough to fit our requirements. As a result, we 
need 1 collection/customer. There is more than a thousand customers and 
it seems unreasonable to create thousands of collections in Solr 
Cloud... But as we know that there are less than 1 query/customer/day, 
we are currently looking for a way to passivate collection when they are 
not in use. Can it be a good idea? If yes, are there best practices to 
implement this? What side effects can we expect? Do we need to put some 
application-level logic on top on the Solr Cloud cluster to choose which 
collection we have to unload (and maybe there is something smarter (and 
quicker?) than simply loading/unloading the core when it is not in used?) ?


Thank you for your answer(s),

Aurelien


--------------000701010100030303000503--