Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 26 Sep 2012 02:21:08 +1100 (NCT)
From: "Hoss Man (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <1809952388.122660.1348586468514.JavaMail.jiratomcat@arcas>
In-Reply-To: <140538595.119327.1348527247971.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (SOLR-3884) possible bug in how commits are
 handled during "recovery" mode on startup?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462860#comment-13462860 ] 

Hoss Man commented on SOLR-3884:
--------------------------------

{quote}
I tried the clean directory approach - here's the smokeTestRelease.py patch:
...
But this seemed to have no effect - the failure still happens:
...
Attaching the solr-example.log files from each directory.
{quote}

If these logs you attached on 25/Sep/12 are what you got *with* the patch then something _really_ weird is going on -- because using a clean example dir there's no logical reason why it should have been doing tlog recovery in either run.
                
> possible bug in how commits are handled during "recovery" mode on startup?
> --------------------------------------------------------------------------
>
>                 Key: SOLR-3884
>                 URL: https://issues.apache.org/jira/browse/SOLR-3884
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>         Attachments: java6.solr-example.log, java7.solr-example.log, solr-example.log
>
>
> while testing out 4.0-rc0, sarowe noted the he was seeing the smoke tester script fail while sanity checking the solr example.
> https://mail-archives.apache.org/mod_mbox/lucene-dev/201209.mbox/%3C6C78E97C707B5B4C8CC61D44F87545863ED73E@SUEX10-mbx-03.ad.syr.edu%3E
> I'm not certain, but looking at his logs, i think this suggests a bug in how commits are handled when a newly started server is in "recovery" mode

--
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