On Wed, Jul 8, 2009 at 10:14 PM, solr jay wrote:
> Thanks. The patch looks good, and I now see the new index directory and it
> is in sync with the one on master. I'll do more testing.
>
> It is probably not important, but I am just curious why we switch index
> directory. I thought it would be eas
jay,
Thanks. The testcase was not enough. I have given a new patch . I
guess that should solve this
On Wed, Jul 8, 2009 at 3:48 AM, solr jay wrote:
> I guess in this case it doesn't matter whether the two directories
> tmpIndexDir and indexDir are the same or not. It looks that the index
> directo
I guess in this case it doesn't matter whether the two directories
tmpIndexDir and indexDir are the same or not. It looks that the index
directory is switched to tmpIndexDir and then it is deleted inside
"finally".
On Tue, Jul 7, 2009 at 12:31 PM, solr jay wrote:
> In fact, I saw the directory w
In fact, I saw the directory was created and then deleted.
On Tue, Jul 7, 2009 at 12:29 PM, solr jay wrote:
> Ok, Here is the problem. In the function, the two directories tmpIndexDir
> and indexDir are the same (in this case only?), and then at the end of the
> function, the directory tmpIndexD
Ok, Here is the problem. In the function, the two directories tmpIndexDir
and indexDir are the same (in this case only?), and then at the end of the
function, the directory tmpIndexDir is deleted, which deletes the new index
directory.
} finally {
delTree(tmpIndexDir);
}
On
I see. So I tried it again. Now index.properties has
#index properties
#Tue Jul 07 12:13:49 PDT 2009
index=index.20090707121349
but there is no such directory index.20090707121349 under the data
directory.
Thanks,
J
On Tue, Jul 7, 2009 at 11:50 AM, Shalin Shekhar Mangar <
shalinman...@gmail.co
On Tue, Jul 7, 2009 at 11:50 PM, solr jay wrote:
> It seemed that the patch fixed the symptom, but not the problem itself.
>
> Now the log messages looks good. After one download and installed the
> index,
> it printed out
>
> *Jul 7, 2009 10:35:10 AM org.apache.solr.handler.SnapPuller
> fetchLat
t; >>> >> jay , I see updating index properties... twice
> >>> >>
> >>> >>
> >>> >>
> >>> >> this should happen rarely. in your case it should have happened only
> >>> >> once. because you cleaned up the master only once
> >>
>>
>>> >> On Fri, Jul 3, 2009 at 6:09 AM, Otis
>>> >> Gospodnetic wrote:
>>> >> >
>>> >> > Jay,
>>> >> >
>>> >> > You didn't mention which version of Solr you are using. It looks
>>> >>
> >> > some trunk or nightly version. Maybe you can try the latest nightly?
>> >> >
>> >> > Otis
>> >> > --
>> >> > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>> >> >
>> >> >
>>
>> From: solr jay
> >> To: solr-user@lucene.apache.org
> >> Sent: Thursday, July 2, 2009 9:14:48 PM
> >> Subject: reindexed data on master not replicated to slave
> >>
> >> Hi,
> >>
> >> When index data were corrupted on master instance,
ne.apache.org
>> Sent: Thursday, July 2, 2009 9:14:48 PM
>> Subject: reindexed data on master not replicated to slave
>>
>> Hi,
>>
>> When index data were corrupted on master instance, I wanted to wipe out all
>> the index data and re-index everything. I was hopin
the latest nightly?
>
> Otis
> --
> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>
>
>
> - Original Message
> > From: solr jay
> > To: solr-user@lucene.apache.org
> > Sent: Thursday, July 2, 2009 9:14:48 PM
> > Subject: reindexed d
: solr-user@lucene.apache.org
> Sent: Thursday, July 2, 2009 9:14:48 PM
> Subject: reindexed data on master not replicated to slave
>
> Hi,
>
> When index data were corrupted on master instance, I wanted to wipe out all
> the index data and re-index everything. I was hoping the newly created
Hi,
When index data were corrupted on master instance, I wanted to wipe out all
the index data and re-index everything. I was hoping the newly created index
data would be replicated to slaves, but it wasn't.
Here are the steps I performed:
1. stop master
2. delete the directory 'index'
3. start
15 matches
Mail list logo
