Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: neutral (nike.apache.org: 67.222.54.6 is neither permitted nor
 denied by domain of nicholas.ball@nodelay.com)
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Date: Mon, 02 Jul 2012 04:37:12 -0600
From: Nicholas Ball <nicholas.ball@nodelay.com>
To: <solr-user@lucene.apache.org>
Subject: Re: Atomic Multicore Operations - E.G. Move Docs
In-Reply-To: 
 <CAK9GPcRVb2mbh=wmbKOq2vCVu7PNvszViVYYYpbDkeBeMgAQLw@mail.gmail.com>
References: <f14d84ae6fd18244ff28360440c542d9@mail.nodelay-solutions.com>
 <CAK9GPcRVb2mbh=wmbKOq2vCVu7PNvszViVYYYpbDkeBeMgAQLw@mail.gmail.com>
Message-ID: <160985ea7cf1ed6c8a1944436ecadc54@mail.nodelay-solutions.com>
User-Agent: SilvertipCode Webmail/0.4-beta


That could work, but then how do you ensure commit is called on the two
cores at the exact same time?
Also, any way to commit a specific update rather then all the back-logged
ones?

Cheers,
Nicholas

On Sat, 30 Jun 2012 16:19:31 -0700, Lance Norskog <goksron@gmail.com>
wrote:
> Index all documents to both cores, but do not call commit until both
> report that indexing worked. If one of the cores throws an exception,
> call roll back on both cores.
> 
> On Sat, Jun 30, 2012 at 6:50 AM, Nicholas Ball
> <nicholas.ball@nodelay.com> wrote:
>>
>> Hey all,
>>
>> Trying to figure out the best way to perform atomic operation across
>> multiple cores on the same solr instance i.e. a multi-core environment.
>>
>> An example would be to move a set of docs from one core onto another
core
>> and ensure that a softcommit is done as the exact same time. If one
were
>> to
>> fail so would the other.
>> Obviously this would probably require some customization but wanted to
>> know what the best way to tackle this would be and where should I be
>> looking in the source.
>>
>> Many thanks for the help in advance,
>> Nicholas a.k.a. incunix