Instant Search Locked

Permanently deleted user

2. August 2017 15:40

Instant Search seems to be locked up and not scanning. The error logs are filled with this message:

 

  [0]}] on [[geocortex.core.roles.elasticsearch.watcher][0]] [geocortex.core.roles.elasticsearch.watcher][[geocortex.core.roles.elasticsearch.watcher][0]] FlushNotAllowedEngineException[already flushing...] at org.elasticsearch.index.engine.InternalEngine.flush(InternalEngine.java:748) at org.elasticsearch.index.shard.IndexShard.flush(IndexShard.java:788) at org.elasticsearch.action.admin.indices.flush.TransportShardFlushAction.shardOperationOnPrimary(TransportShardFlushAction.java:63) at org.elasticsearch.action.admin.indices.flush.TransportShardFlushAction.shardOperationOnPrimary(TransportShardFlushAction.java:42) at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryPhase.doRun(TransportReplicationAction.java:639) at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:279) at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:271) at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:75) at org.elasticsearch.transport.TransportService$4.doRun(TransportService.java:376) at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

 

We tried restarting the core service but the error is still occurring. Is there a way to delete the old search index and start it over?

0

• 

  Frank Martin

  2. August 2017 16:39

  Mark, 

   

  Below are the steps I used to recreate our instant search data.

   

  - stop the Geocortex service (task manager / services tab)

   

  - delete the following indexes

   

        C:\Program Files\Latitude Geographics\Geocortex Core\Data\DocumentStore\DocumentStore\[YourClusterName]\nodes\0\indices\geocortex.essentials.default.instantsearch

   

        C:\Program Files\Latitude Geographics\Geocortex Core\Data\DocumentStore\DocumentStore\[YourClusterName]\nodes\0\indices\geocortex.search

   

        C:\Program Files\Latitude Geographics\Geocortex Core\Data\DocumentStore\DocumentStore\[YourClusterName]\nodes\0\indices\geocortex.search.messagequeue

   

  - restart the Core service

   

  - visit the Instant Search page and make sure all is OK

   

   

   

  This will result in all your Instant Search data being purged and it will need to be recreated.  It will also result in your viewers and Manager not being available for a few minutes.  No other data should be lost with this change.

   

  Hope this helps.

   

  Regards,

   

  Frank

  0
• 

  Permanently deleted user

  8. August 2017 14:09

  Thanks Frank - this worked with one caveat I'll leave for others - one must delete the index folders or move them to another location. I tried to be cautious and just renamed the index folders. This makes ElasticSearch unhappy so the core services won't completely start. Once I moved the folders out it worked again.

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.