cleanup old index directories on slaves

Is there a reliable way to safely clean up index directories? This is needed mainly on slave side as in several situations, an old index directory is replaced with a new one, and I'd like to remove those that are no longer in use. Thanks, -- J

Re: enablereplication does not work

By the way, I was using command=indexversion to verify replication is on or off. Since it seems not reliable, is there a better to do it? Thanks, On Thu, Aug 6, 2009 at 8:43 AM, solr jay wrote: > You are right. Replication was disabled after the server was restarted, and > then I s

Re: enablereplication does not work

cationhandler configured? if there was no > commit/optimize thhen it would show the version as '0' > > On Thu, Aug 6, 2009 at 5:50 AM, solr jay wrote: > > Hi, > > > > http://localhost:8549/solr/replication?command=enablereplication > > > > does not seem wor

enablereplication does not work

Hi, http://localhost:8549/solr/replication?command=enablereplication does not seem working. After making the request, I run http://localhost:8549/solr/replication?command=indexversion and here is the response: 0 0 0 0 Notice the indexversion is 0, which is the value after you disable re

index backup works only if there are committed index

Hi, I noticed that the backup request http://master_host:port/solr/replication?command=backup works only if there are committed index data, i.e. core.getDeletionPolicy().getLatestCommit() is not null. Otherwise, no backup is created. It sounds

Re: index version on slave

> > > On Tue, Jul 21, 2009 at 12:53 AM, solr jay wrote: > > If you ask for the index version of a slave instance, you always get > version > > number being 0. Is it expected behavior? > > > > I am using this url > > > > http://slave_host:8983/solr/

index version on slave

If you ask for the index version of a slave instance, you always get version number being 0. Is it expected behavior? I am using this url http://slave_host:8983/solr/replication?command=indexversion This request returns correct version on master. If you use the 'details' command, you get the ri

Re: reindexed data on master not replicated to slave

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

Re: reindexed data on master not replicated to slave

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

Re: reindexed data on master not replicated to slave

Tue, Jul 7, 2009 at 12:17 PM, solr jay 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. &g

Re: reindexed data on master not replicated to slave

man...@gmail.com> wrote: > 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 pr

Re: reindexed data on master not replicated to slave

owse/SOLR-1264 > > I have attached a patch as well . I guess that is the fix. could you > please confirm that. > > > On Tue, Jul 7, 2009 at 12:59 AM, solr jay wrote: > > It looks that the problem is here or before that in > > SnapPuller.fetchLatestIndex(): > > &

Re: reindexed data on master not replicated to slave

J On Mon, Jul 6, 2009 at 8:02 AM, solr jay wrote: > There is only one index directory: index/ > > Here is the content of index.properties > > #index properties > #Fri Jul 03 14:17:12 PDT 2009 > index=index.20090703021705 > > > Thanks, > > J > > 2009/7/5

Re: reindexed data on master not replicated to slave

rsion of Solr you are using. It looks like > some trunk or nightly version. Maybe you can try the latest nightly? > > > > Otis > > -- > > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > > > > > > - Original Message >

Re: reindexed data on master not replicated to slave

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

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

solr health check

Hi, I am looking at this piece of configuration in solrconfig.xml solr solrconfig.xml schema.xml q=solr&version=2.0&start=0&rows=0 server-enabled It wasn't clear to me what 'server-enabled' means here. Is it a file name? If it is file name, wher