Return-Path: Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org Received: (qmail 95749 invoked from network); 1 Aug 2009 06:28:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Aug 2009 06:28:34 -0000 Received: (qmail 30276 invoked by uid 500); 1 Aug 2009 06:28:37 -0000 Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org Received: (qmail 30196 invoked by uid 500); 1 Aug 2009 06:28:37 -0000 Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-dev@lucene.apache.org Received: (qmail 30180 invoked by uid 99); 1 Aug 2009 06:28:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 06:28:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 06:28:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D5B25234C004 for ; Fri, 31 Jul 2009 23:28:14 -0700 (PDT) Message-ID: <367334444.1249108094870.JavaMail.jira@brutus> Date: Fri, 31 Jul 2009 23:28:14 -0700 (PDT) From: "Otis Gospodnetic (JIRA)" To: solr-dev@lucene.apache.org Subject: [jira] Commented: (SOLR-1293) Support for large no:of cores and faster loading/unloading of cores In-Reply-To: <1744474626.1247826434925.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/SOLR-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737838#action_12737838 ] Otis Gospodnetic commented on SOLR-1293: ---------------------------------------- Do you have any thoughts on handling the situation where each core belongs to a different party and each party has access *only* to its own core via Solr Admin (i.e. doesn't see all the other cores hosted by the instance)? Only the privileged administrator user can see and access all cores. Have you done any work in on this or is this on your TODO? > Support for large no:of cores and faster loading/unloading of cores > ------------------------------------------------------------------- > > Key: SOLR-1293 > URL: https://issues.apache.org/jira/browse/SOLR-1293 > Project: Solr > Issue Type: New Feature > Reporter: Noble Paul > Fix For: 1.5 > > Attachments: SOLR-1293.patch > > > Solr , currently ,is not very suitable for a large no:of homogeneous cores where you require fast/frequent loading/unloading of cores . usually a core is required to be loaded just to fire a search query or to just index one document > The requirements of such a system are. > * Very efficient loading of cores . Solr cannot afford to read and parse and create Schema, SolrConfig Objects for each core each time the core has to be loaded ( SOLR-919 , SOLR-920) > * START STOP core . Currently it is only possible to unload a core (SOLR-880) > * Automatic loading of cores . If a core is present and it is not loaded and a request comes for that load it automatically before serving up a request > * As there are a large no:of cores , all the cores cannot be kept loaded always. There has to be an upper limit beyond which we need to unload a few cores (probably the least recently used ones) > * Automatic allotment of dataDir for cores. If the no:of cores is too high al the cores' dataDirs cannot live in the same dir. There is an upper limit on the no:of dirs you can create in a unix dir w/o affecting performance -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.