A couple of things come to mind:
1> are you absolutely certain that you're opening the index
file you *think* you are? I'd try being really crude and renaming
the index file and restarting my server. Perhaps you're
pointing to the index on the *old* server when searching.
2> Are you absolutely sure you're closing and reopening your
readers after the update? You'd be able to tell this by restarting
your server and seeing if your searches worked then.
3> Get a copy of Luke and examine your index, that'll tell you a lot
about how it's changing (or not).....
Sounds to me like somehow there's a mismatch between the index you're
updating and the one you're searching, but that's a WAG.
Best
Erick
On Wed, Sep 17, 2008 at 12:45 PM, Chris Mannion <
[EMAIL PROTECTED]> wrote:
> Hi All
>
> I'm having a problem with our lucene index and wondering if anyone else has
> encountered anything similar or has any idea of what I might look at to
> find
> the cause/solution. We had a working tomcat setup in which records were
> regularly uploaded into a lucene index, each upload removed old records
> from
> the index and inserted new ones, and a website running on the tomcat server
> had a page to search and display records from that index. Recently the
> whole setup has been moved to a new server by simply copying the complete
> tomcat directory across (the lucene index files are stored within the
> tomcat
> directory structure) and since then the process has fallen appart, uploads
> are still loaded in as before, removing old data and inserting new, without
> any errors occuring and with the insert and remove calls returning the
> correct numbers of records processed, but when we search the index, it
> seems
> as though no uploads have been done, the data the search returns is the old
> data. Even more oddly, monitoring the numbers of records in the index as
> reported by the upload process seems to imply that the data is changing
> correctly, but the search doesn't reflect this.
>
> For example, originally the index contained 1292 records of a certain type.
> On uploading a new set of 1219 of the records, the index reported that 1292
> of that type had been removed and 1219 inserted. Subsequent uploads of the
> same new set of data reported that 1219 records had been dropped from the
> index and again 1219 inserted, implying that the initial upload had worked
> as expected. However, the search still continue to find 1292 records. We
> flush and optimize the index after each upload and for the past year the
> system has worked fine, it's only since being copied onto a new server that
> this odd behaviour has started. Any ideas would be gratefully received,
> I'm
> completely puzzled.
>
> --
> Chris Mannion
> iCasework and LocalAlert implementation team
> 0208 144 4416
>
