You need to issue just a commit command to solr-2
This will refresh its cache and you will be good to go
The sequence:
1) Index and commit on solr-1
2) Just issue commit on solr-2.
-----Original Message-----
From: Jae Joo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 14, 2007 6:07 AM
To: solr-user@lucene.apache.org
Subject: Re: two solr instances - index and commit
Solr-1 - for indexing instance - localhost:8880/solr_1
solr-2 - for search - localhost:8080/solr_2 (different port number than
solr-1)
Here is the list of steps what I tried.
1. in the Solr-1, index and commit it. I could see all indexes in the
data/index directory.
How can I commit the index on solr-2 which is already committed in solr1?
Thanks
Jae
On Nov 13, 2007 6:48 PM, Kasi Sankaralingam <[EMAIL PROTECTED]> wrote:
> This works, the only thing you need to be aware of is the NFS problem if
> you are
> running in a distributed environment sharing a NFS partition.
>
> a) Index and commit on instance (Typically partitioned as an index server)
>
> b) Issue a commit on the search server (like a read only mode)
>
> Things to watch out for, you will get stale NFS problem, I replaced lucene
> core
> that is shipped with solr to the latest one and it works.
>
> -----Original Message-----
> From: Jae Joo [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 13, 2007 9:06 AM
> To: solr-user
> Subject: two solr instances - index and commit
>
> Hi,
>
> I have two solr instance running under different tomcat environment.
> One solr instance is for indexing and would like to commit to the other
> solr
> instance.
>
> This is what I tried, but failed.
> using post.sh (without commit), the docs are indexed in solr-1 instance.
> After indexed,
> call commit command with the attribute of solr-2.
>
> Can any help me?
>
> Jae
>
