is there anyway to manually remove an index - it is stuck at 0%

Permanently deleted user

4. März 2019 17:02

i have a layer that is trying to build an index buth has not moved from 0%   since thursday  (the exact same layer is accesses the the web portal and it has indexed successfully)  i went thru the logs but there does not seem to be any error messages.  I press the pause (there is no database delete icon) and nothing chages (the logs reflect a pause momentarily but then condintue on.   How do i clean out the old index file/database and start from scratch?

0

• 

  Permanently deleted user

  4. März 2019 22:11

  Hi Mike, 

   

  You can manually delete all Instant Search related indexes by doing the following:

   

  1) stop the Geocortex Core service 

   

  2) delete the following 3 folders : 

   

  C:\Program Files\Latitude Geographics\Geocortex Core\Data\DocumentStore\DocumentStore\{ClusterName}\nodes\0\indices\geocortex.essentials.default.instantsearch 

   

  C:\Program Files\Latitude Geographics\Geocortex Core\Data\DocumentStore\DocumentStore\{ClusterName}\nodes\0\indices\geocortex.search 

   

  C:\Program Files\Latitude Geographics\Geocortex Core\Data\DocumentStore\DocumentStore\{ClusterName}\nodes\0\indices\geocortex.search.messagequeue 

   

  3) rename the logs folder so we get a new one created (C:\Program Files\Latitude Geographics\Geocortex Core\Data\Logs) 

   

  4) restart the Geocortex Core service 

   

  This will clean out all Instant Search indexes, you cannot delete individual services.

   

  If you are not comfortable doing this, feel free to open a support ticket.

   

  Regards,

   

  Wayne Richard

   

  Latitude Geographics Group Ltd.

   

  Head Office: 300 – 1117 Wharf Street  Victoria, BC Canada V8W 1T7

   

  Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com 

   

  Developers of Geocortex web-based mapping software | www.geocortex.com

   

  An Esri Platinum Business Partner

   

   

  0
• 

  Permanently deleted user

  28. Juni 2019 08:48

  I'm afraid we need a better approach. It's not ideal to wipe out  the entire instant search indexes only because of one or two bad indexing jobs, espeically when you have the other 30 instant searches that have just been built after several weeksare are just fine. Please provide us an solution to delete search indexing if it faile.  Here, add the delete option to delete the indexing job if it failed. Plus, there's no purpose to keep the broken indexing job try to run every hour/day/week at the background.  Otherwise using Instant Search just introduce nightmare to maintiance and admin, and direct me away from it.

   

  

  0

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