Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of erickerickson@gmail.com
 designates 209.85.216.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=EWwaVFSemTU4v1nSlzIOx3nCI4zveYadJec0ISBva7BiAufuCOHcfADBgU7gBLY/kA
         k9qT4A1gUA8tbT0wMa8+Wbny7IGkQ72XsmvJdxikuXPO4WB7teOn0/KfhLnxAlydN0Rb
         BDMZscZueBvzdNXQu3XcHqLv48nqFkcGq9yp0=
MIME-Version: 1.0
In-Reply-To: <BANLkTin9dfRdhV1bTRdAmG1PA9Fb=xTUTw@mail.gmail.com>
References: <BANLkTin9dfRdhV1bTRdAmG1PA9Fb=xTUTw@mail.gmail.com>
Date: Tue, 12 Apr 2011 09:07:42 -0400
Message-ID: <BANLkTikNqvshOzkAa1_2MU8w1vBx04ciYQ@mail.gmail.com>
Subject: Re: SolrException: Unavailable Service
From: Erick Erickson <erickerickson@gmail.com>
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=0022153de27ba265fd04a0b860ee

--0022153de27ba265fd04a0b860ee
Content-Type: text/plain; charset=ISO-8859-1

If your commit from the client fails, you don't really know the
state of your index anyway. All the threads you have sending
documents to Solr are adding them to a single internal buffer.
Committing flushes that buffer.

So if thread 1 gets an error on commit, it will presumably
have some documents from thread 2 in the commit. But
thread 2 won't necessarily see the results. So I don't think
your statement about needing to know if a commit fails
is really

On Tue, Apr 12, 2011 at 8:50 AM, Phong Dais <phong.gdais@gmail.com> wrote:

> Hi,
>
> I did not want to hijack this thread (
> http://www.mail-archive.com/solr-user@lucene.apache.org/msg34181.html)
> but I am experiencing the same exact problem mentioned here.
>
> To sum up the issue, I am getting intermittent "Unavailable Service"
> exception during indexing commit phase.
> I know that I am calling commit "very often" but I do not see any way
> around
> this.  This is my situation, I am
> indexing a huge amount of documents using multiple instance of SolrJ client
> running on multiple servers.  There is no way
> for me control when "commit" is called from these clients, so two different
> clients can call commit "at the same time".
> I am not sure if I can/should use auto/timed commit because I need to know
> if a commit failed so I can rollback the batch that failed.
>
> What kind of options do I have?
> Should I try to catch the exception and keep trying to "recommit" until it
> goes through?  I can see some potential of problems with this approach.
> Do I need to write a request broker to queue up all these commit and send
> them to solr one by one in a "timely" manner?
>
> Just wanted to know if anyone has a solution for this problem before I dive
> off the deep end.
>
> Thanks,
> Phong
>

--0022153de27ba265fd04a0b860ee--