Enterprise Vault Indexing Service is slow to become fully functional and update indexes due to high CPU usage.

book

Article ID: 100055058

calendar_today

Updated On:

Description

Error Message

No error is returned. However, it may take the Indexing Service several hours to go from a starting 41297 event to a 41302 event showing the service is fully functional.  In the example below, the startup took over 3 hours to complete. 

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault 
Date:          2/7/2023 8:46:54 AM
Event ID:      41297
Task Category: Index Admin Service 
Level:         Information
Computer:      EVSERVER02.EVLOCAL.COM
Description:
The Indexing Service has started.

 

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault 
Date:          2/7/2023 11:51:19 AM
Event ID:      41302
Task Category: Index Admin Service 
Level:         Information
Computer:      EVSERVER02.EVLOCAL.COM
Description:
The Indexing Service has completed its initialization. The service is now functioning fully. 

During this time, a 41374 event will occur every 10 minutes stating the metadata is being synchronized.  

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault 
Date:          2/7/2023 10:55:00 AM
Event ID:      41374
Task Category: Index Admin Service 
Level:         Information
Computer:     EVSERVER02.EVLOCAL.COM
Description:
Indexing Service is synchronizing index volume metadata between the indexing engine repository and the Directory database. 

V-437-41297
V-437-41302
V-437-41374

A Dtrace on the EVIndexAdminService process during startup will show high TraceTimer times. In this case, the times show 29 seconds to complete the operation per volume.  Normal times should only show milliseconds to complete the operation. 

(EVIndexAdminService)        EV-L    {IndexingWCFProxy`1} TraceTimer [28975ms] Called SearchCollectionXml
(EVIndexAdminService)        EV-L    {IndexingWCFProxy`1} TraceTimer [29035ms] Called SearchCollectionStatus

Cause

This issue could be caused by any application that will slow down or block requests by the indexing processes.  

Resolution

Stop the service/driver to determine if this resolves the issue. If this allows the indexing process to start normally, then one of the following steps should be taken.  

  1. Upgrade the software to a later version.
  2. Remove the software from the EV server if it is not required.  

Issue/Introduction

The Enterprise Vault (EV) Indexing Service will take a very long time to become fully functional due to the high CPU utilization by many of the indexing processes.
Powered by Wolken Software