Skip to main content

Instant search on a service shows "indexing" all the time

Permanently deleted user
I'm not sure when it started, but it used to be that when I went in to re-run the instant search index for a map service, the status would show as "Idle". I could then click the arrow to re-scan.

 

Now when I go into the instant search, it always shows "indexing". I have to delete the index and re-index completely. Fortunately, my re-indexing only takes minutes, but I want to know what is wrong and how to fix it.

 

Any clues?
0

Comments

2 comments

Date Votes
  • Permanently deleted user
    Hi there Heather,

     

    For Instant search issues, there are a few things that I usually check:

     

    1) Is the disk where your Core data is stored nearly full?  If the disk has less than 15% free space you can see some odd behaviour with ElasticSearch (the component that stores your Instant Search data)

     

    2) Are there any exceptions in the InstantSearch logs in the logs folder (here by default: C:\Program Files\Latitude Geographics\Geocortex Core\Data\Logs)

     

    If you're still having trouble after checking those things, I would suggest opening a support case so we can help!

     

    Thanks,

     

    Danny
    0
  • Permanently deleted user

    I have a similar problem with one of my layers , it is a very big polygon layer of customers and the ElasticSearch seem to block at 11% every time.  

    The error was:  - ArcGis feature query response contained an error: 500 Error performing query operation Encountered fatal error at 14:54:44 for URL 'http://pdc03srv152:6080/arcgis/rest/services/Geocortex/Customers/MapServer/4/query?objectIds=130794%...'. Attempted maximum number of retries; index may be incomplete.  

    The solution could be to increase  the SOC heap size in ArcGIS server (see  http://support.esri.com/en/technical-article/000011736 )

     

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post