Note that there are some explanatory texts on larger screens.

plurals
  1. POHibernate Search issue on Amazon
    primarykey
    data
    text
    <p><strong><em>Technology Versions</em>:<br></strong></p> <pre> Hibernate 3.6.5<br> Hibernate Search 3.4.0<br> Lucene (lucene-core-*.jar) 3.1.0<br> Spring 3.1.0.M2 </pre> <p><strong><em>Hibernate (Search) Configuration</em>:<br></strong></p> <pre><code>&lt;prop key="hibernate.search.default.indexBase"&gt;/some/dir&lt;/prop&gt; &lt;prop key="hibernate.search.default.directory_provider"&gt;org.hibernate.search.store.FSDirectoryProvider&lt;/prop&gt; &lt;prop key="hibernate.search.default.locking_strategy"&gt;native&lt;/prop&gt; &lt;prop key="hibernate.search.default.exclusive_index_use"&gt;false&lt;/prop&gt; </code></pre> <p><strong><em>The issue</em>:<br></strong> Our application is deployed in Amazon (AWS cloud), but we've faced this issue in our local clusters as well:</p> <p>The application design is such that there is a <code>Thread</code> that is spawned from within the main (Web) application wherefrom we need to update an <em>Indexed</em> entity. Basically it's like a status monitor thread which reads a .status file and updates the database every 30 seconds or so. This keeps happening for about 10mins to 1/2 an hour on an average. The issue we see is that: every few days we need to regenerate the indexes because Hibernate Search stops returning anything for the entity in question (the one discussed above).</p> <p>I went through few forums and seems it is suggested that only a single thread should be updating the Lucene indexes. But it is also given that index writing is thread-safe. So even if multiple threads are writing to the same index, I still expect that it should not cause the issue (of nothing being returned in the search). That is to say, I may get stale status of the entity in question, but still, <em>something</em> should be returned.</p> <p>We're using the default IndexReader/Writer implementation of Hibernate Search.</p> <p>Any help would be highly appreciated. Thanks.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload