Error: "communication with indexer process failed" due to CPU saturation during replication

Products

• Data Loss Prevention Core Package

Issue/Introduction

DLP Enforce logs show Error: communication with indexer process failed or connection losses between Enforce and detection servers. These errors typically coincide with large profile replication tasks.

Environment

DLP 16.1MP2+

Cause

During Data Profile replication, the Enforce server may consume 100% of available CPU resources. When the CPU is saturated, internal processes (like the EDM/IDM Indexer process) cannot communicate in a timely manner, leading to timeouts and connection failures.

Resolution

 Starting with DLP 16.1 MP2, you can throttle the data transfer rates for replication to optimize CPU usage.

1. Open MonitorController.properties on the Enforce server.
2. Add the following parameters to the bottom of the file:
   • uds.comm.all.inbound.data.rate.throttle.limit.in.kbps
   • uds.comm.all.outbound.data.rate.throttle.limit.in.kbps
   • uds.comm.per.connection.inbound.data.rate.throttle.limit.in.kbps
   • uds.comm.per.connection.outbound.data.rate.throttle.limit.in.kbps
3. A recommended starting value for uds.comm.all.outbound.data.rate.throttle.limit.in.kbps is 393216.
4. Save the file and restart the Symantec DLP Manager service.