Lucene index updates not reflected on other Lucee servers.

Description

  1. When using a UNC path to the Lucene collection data stored on a SAN, updates made to that index on Server 1 are not reflected on Server 2 pointed at the same path.

How does one get Server 2 to reload the freshly updated index?

The Lucene Search Engine extension is version 2.4.1.29.

Environment

WIndows 2012 R2

Activity

Adam Winter 3 March 2017 at 15:30

This is an issue which is preventing us from upgrading this application from ColdFusion 10. Until we can have a multi-server solution for this, it has to stay on ColdFusion 10, unfortunately.

Adam Winter 20 January 2017 at 19:18

It seems the heart of the issue here is one of two scenarios happening.

  1. The index is held in RAM. If that's the case, the second server isn't loading the index when it's updated by the first server because it never looks again at the files on the SAN. There should either be an index version number or hash that is compared for each search so the server knows when an index update has occurred and it needs to reload it. The idea here is a frequent, but very small read on the SAN.

  2. The index is read every time. This is not likely the case, since we're not seeing the updates on the second server. However, if it was, that would be a lot of read hits by both servers. This would likely result in a lot of unnecessary reads across the SAN.

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 20 January 2017 at 19:04
Updated 18 June 2023 at 16:23