In our upgraded fully patched 7.2 system (patched to CMS-475) Lucene will at random points (I think after a period of inactivity) start erroring with the following message and refuse to index any further content, with the same error each time, until the system is restarted.
Once restarted, items that previously displayed the error are able to be indexed again, until the index writer timeout happens again.
2013-08-14 08:56:25,499 ERROR [com.percussion.search.PSSearchIndexEventQueue] Error indexing id 65744 and it has been skipped
org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed
at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:262)
at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:1755)
at com.percussion.search.lucene.PSSearchIndexerImpl.commit(Unknown Source)
at com.percussion.search.PSSearchIndexEventQueue.indexItemDeletion(Unknown Source)
at com.percussion.search.PSSearchIndexEventQueue.processNextEventSet(Unknown Source)
at com.percussion.search.PSSearchIndexEventQueue.access$100(Unknown Source)
at com.percussion.search.PSSearchIndexEventQueue$1.run(Unknown Source)
I thought I might be able to force periodic index writer activity by scheduling a “search index type 315” to run every few minutes, thus not letting the index writer idle for any length of time (while not forcing it to index tonnes of content since that command just reindexes a few NavTrees). But using the Scheduled Task extension sys_runCommand to try to run search index type 315 just results in an error - cannot run program “search”…the system cannot find the file specified etc.
Anyone seen their index writer time out like this before? Anyone managed to schedule a console command to run periodically?
Cheers, Andrew
This looks like a bug introduced by the Indexing fixes in a recent patch. I would log an issue with support for this if you haven’t already.
-n
[QUOTE=allana;20825]In our upgraded fully patched 7.2 system (patched to CMS-475) Lucene will at random points (I think after a period of inactivity) start erroring with the following message and refuse to index any further content, with the same error each time, until the system is restarted.
Once restarted, items that previously displayed the error are able to be indexed again, until the index writer timeout happens again.
2013-08-14 08:56:25,499 ERROR [com.percussion.search.PSSearchIndexEventQueue] Error indexing id 65744 and it has been skipped
org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed
at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:262)
at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:1755)
at com.percussion.search.lucene.PSSearchIndexerImpl.commit(Unknown Source)
at com.percussion.search.PSSearchIndexEventQueue.indexItemDeletion(Unknown Source)
at com.percussion.search.PSSearchIndexEventQueue.processNextEventSet(Unknown Source)
at com.percussion.search.PSSearchIndexEventQueue.access$100(Unknown Source)
at com.percussion.search.PSSearchIndexEventQueue$1.run(Unknown Source)
I thought I might be able to force periodic index writer activity by scheduling a “search index type 315” to run every few minutes, thus not letting the index writer idle for any length of time (while not forcing it to index tonnes of content since that command just reindexes a few NavTrees). But using the Scheduled Task extension sys_runCommand to try to run search index type 315 just results in an error - cannot run program “search”…the system cannot find the file specified etc.
Anyone seen their index writer time out like this before? Anyone managed to schedule a console command to run periodically?
Cheers, Andrew[/QUOTE]