If it helps, I am running: solr 1.4.0 tomcat 6.0.26
java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) Red Hat Enterprise Linux Server release 5.4 (Tikanga) thanks, Tim On Mon, May 3, 2010 at 4:47 PM, Tim Heckman <theck...@gmail.com> wrote: > I have 2 cores: core1 and core2. > > Load the same data set into each and commit. Verify that searches > return the same for each core. > > Delete a document (call it docA) from core2 but not from core1. > > Commit and verify search results (docA disappears from core2's search > results. core1 continues to return the docA) > > Swap cores. > > Core2 should now return docA, but it doesn't until I reload core2. > > > thanks, > Tim > > > On Mon, May 3, 2010 at 1:41 PM, Shalin Shekhar Mangar > <shalinman...@gmail.com> wrote: >> On Mon, May 3, 2010 at 10:27 PM, Tim Heckman <theck...@gmail.com> wrote: >> >>> Hi, I'm trying to figure out whether I need to reload a core (or both >>> cores?) after performing a swap. >>> >>> When I perform a swap in my sandbox (non-production) environment, I am >>> seeing that one of the cores needs to be reloaded following a swap and >>> the other does not, but I haven't been able to find a pattern to which >>> one it will be. >>> >>> >> No, you should not need to reload any core after a swap. What is the >> behavior that you see? >> >> -- >> Regards, >> Shalin Shekhar Mangar. >> >
