Re: Running into problems with distributed index and search
How is the performace? For me, Solr got about 100 times faster for update when I moved the files from NFS to local disk. wunder On 8/22/07 2:27 PM, Kasi Sankaralingam [EMAIL PROTECTED] wrote: Instance (index server) for indexing. The index file data directory reside on a NFS partition, I am running into the following problems,
RE: Running into problems with distributed index and search
Thanks a lot, yes I found that yesterday after doing some experiments. -Original Message- From: Chris Hostetter [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 22, 2007 11:10 PM To: solr-user@lucene.apache.org Subject: Re: Running into problems with distributed index and search : 3) I had to bounce the tomcat search SOLR Webapp instance for it to : read the index files, is it mandatory? In a distributed environment, do : we always have to : : Bounce the SOLR Webapp instances to reflect the changes in the index : files? it sounds like you esentially have a master/slave setup except that instead of using the distribution scripts to copy the index from one to the other, they both use the same physical files via an NFS mount. if you send a commit command to your slave search server, it will reopen the index (without needing to bounce the port) -Hoss
RE: Running into problems with distributed index and search
I have not seen performance degradation, but I will keep that in mind, thanks -Original Message- From: Walter Underwood [mailto:[EMAIL PROTECTED] Sent: Thursday, August 23, 2007 8:56 AM To: solr-user@lucene.apache.org Subject: Re: Running into problems with distributed index and search How is the performace? For me, Solr got about 100 times faster for update when I moved the files from NFS to local disk. wunder On 8/22/07 2:27 PM, Kasi Sankaralingam [EMAIL PROTECTED] wrote: Instance (index server) for indexing. The index file data directory reside on a NFS partition, I am running into the following problems,
Running into problems with distributed index and search
Hi All, This is the scenario, I have two search SOLR instances running on two different partitions, I am treating one of the servers strictly read-only (for search) (search server) and the other Instance (index server) for indexing. The index file data directory reside on a NFS partition, I am running into the following problems, 1) Index dir is /indexdata/data, when I index using the Index server, the index server understands the data dir mentioned in solrconfig.xml, writes the index files To the location and is able to read the files ( I am able to do queries using SOLR Admin) 2) Search server respects the NFS directory, but does not read the index files, SOLR Admin returns no search results, I had to create a sym link to the NFS partition Under $SOLRHOME to point to NFS partition to work. 3) I had to bounce the tomcat search SOLR Webapp instance for it to read the index files, is it mandatory? In a distributed environment, do we always have to Bounce the SOLR Webapp instances to reflect the changes in the index files? Any help/suggestions would be greatly appreciated. Thanks, kasi
