Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3340CEC7F for ; Wed, 28 Nov 2012 15:27:04 +0000 (UTC) Received: (qmail 49092 invoked by uid 500); 28 Nov 2012 15:27:02 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 48984 invoked by uid 500); 28 Nov 2012 15:27:02 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 48960 invoked by uid 99); 28 Nov 2012 15:27:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 15:27:01 +0000 Date: Wed, 28 Nov 2012 15:27:01 +0000 (UTC) From: "Mark Miller (JIRA)" To: dev@lucene.apache.org Message-ID: <1030968801.32867.1354116421914.JavaMail.jiratomcat@arcas> In-Reply-To: <2007386328.27566.1354021803562.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (SOLR-4114) Collection API: Allow multiple shards from one collection on the same Solr server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505539#comment-13505539 ] Mark Miller commented on SOLR-4114: ----------------------------------- bq. you add more machines, they will move to other machines. Personally, I'm not really sold on this auto re balancing idea. I'd prefer the user had to explicitly make these moves. > Collection API: Allow multiple shards from one collection on the same Solr server > --------------------------------------------------------------------------------- > > Key: SOLR-4114 > URL: https://issues.apache.org/jira/browse/SOLR-4114 > Project: Solr > Issue Type: New Feature > Components: multicore, SolrCloud > Affects Versions: 4.0 > Environment: Solr 4.0.0 release > Reporter: Per Steffensen > Assignee: Per Steffensen > Labels: collection-api, multicore, shard, shard-allocation > Attachments: SOLR-4114.patch, SOLR-4114.patch > > > We should support running multiple shards from one collection on the same Solr server - the run a collection with 8 shards on a 4 Solr server cluster (each Solr server running 2 shards). > Performance tests at our side has shown that this is a good idea, and it is also a good idea for easy elasticity later on - it is much easier to move an entire existing shards from one Solr server to another one that just joined the cluter than it is to split an exsiting shard among the Solr that used to run it and the new Solr. > See dev mailing list discussion "Multiple shards for one collection on the same Solr server" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org