What does it mean when it is said in Solr indexing that the index is “eventually consistent”?

In Alfresco, the Solr index operates on an "eventual consistency" model. This means that when content or metadata is updated in the Alfresco repository, the change is not instantly and atomically reflected in the search index. Instead, the repository transaction is recorded, and the Solr indexer processes it asynchronously. There is a brief delay between the repository commit and the index update. The index is considered fully consistent with the repository only when the queue of pending transactions has been completely processed, which occurs when there are no new changes to index.

A server restart is a disruptive event and not the designed mechanism for achieving routine index consistency.

Alfresco's default Solr indexing is a near real-time, asynchronous process, not a daily batch job.

While Solr uses Lucene, this option is too generic. Option B correctly describes the specific state when consistency is achieved: the cessation of new transactions.

1. Alfresco Content Services 5.2 Documentation, "Solr overview": This section describes the architecture where the Alfresco repository and Solr server are separate. It explains that communication is asynchronous, which is the foundation of the eventual consistency model. The repository tracks changes, and Solr polls for them, creating a natural delay.

2. Alfresco Content Services 5.2 Documentation, "Transactional metadata query": This page details how Alfresco can query the database directly for metadata to ensure up-to-the-minute accuracy, acknowledging that the Solr index might lag behind. It states, "The search subsystem is eventually consistent. This means that there is a small delay between making a change to the content and the change being reflected in the search index." This directly confirms the delay inherent in the model.

3. Alfresco Content Services 5.2 Documentation, "Solr core configuration": The configuration properties for Solr, such as alfresco.solr.commit.lockType and settings related to transaction tracking intervals, illustrate the mechanisms that manage this asynchronous, eventually consistent process. The consistency is achieved when the tracking and commit cycles have processed all outstanding repository transactions.