In fact, I saw the directory was created and then deleted.
On Tue, Jul 7, 2009 at 12:29 PM, solr jay <solr...@gmail.com> 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 tmpIndexDir is deleted, which deletes the new index
> directory.
>
>
> } finally {
> delTree(tmpIndexDir);
>
> }
>
>
> On Tue, Jul 7, 2009 at 12:17 PM, solr jay <solr...@gmail.com> wrote:
>
>> 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.com> wrote:
>>
>>> On Tue, Jul 7, 2009 at 11:50 PM, solr jay <solr...@gmail.com> 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
>>> > fetchLatestIndex
>>> > INFO: Slave in sync with master.*
>>> >
>>> > but the files inside index directory did not change. Both
>>> index.properties
>>> > and replication.properties were updated though.
>>> >
>>>
>>> Note that in this case, Solr would have created a new index directory.
>>> Are
>>> you comparing the files on the slave in the new index directory? You can
>>> get
>>> the new index directory's name from index.properties.
>>>
>>> --
>>> Regards,
>>> Shalin Shekhar Mangar.
>>>
>>
>>
>
