Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of btalbot@aeriagames.com
 designates 72.55.177.212 as permitted sender)
Message-Id: <9C9DE43D-B8AA-4EEE-898E-F3F908F22C7B@aeriagames.com>
From: Bryan Talbot <btalbot@aeriagames.com>
To: solr-user@lucene.apache.org
In-Reply-To: <C5A5B6EC.2D1F%jnewburn@zappos.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Changing to multicore
Date: Wed, 28 Jan 2009 08:28:49 -0800
References: <C5A5B6EC.2D1F%jnewburn@zappos.com>

I would think that using a servlet filter to rewrite the URL should be  
pretty strait forward.  You could write your own or use a tool like http://tuckey.org/urlrewrite/ 
  and just configure that.

Using something like this, I think the upgrade procedure could be:
- install rewrite filter to rewrite multi-core URL to non-multi-core  
URL for all solr instances.
- upgrade app to use multi-core URL
- upgrade solr instances to multi-core when convenient and remove  
rewrite filter


-Bryan


On Jan 28, 2009, at Jan 28, 7:17 AM, Jeff Newburn wrote:

> We are moving from single core to multicore. We have a few servers  
> that we
> want to migrate one at a time to ensure that each one functions.  This
> process is proving  difficult as there is no default core to allow the
> application to talk to the solr servers uniformly (ie without a core  
> name
> during conversion).  Would it be possible to re-add the default core  
> as a
> configuration setting in solr.xml to allow for a smoother  
> conversion?  Am I
> missing a setting that would help with this process?
>
> -Jeff