When performing bulk load operations, the Identity Manager notification queue may grow significantly. This backlog can delay password synchronization tasks, preventing users from changing their passwords in a timely manner.
Bulk load tasks are resource-intensive by design. Each user record processed in a bulk load generates multiple notifications for downstream tasks and synchronization. When a large number of these notifications are queued simultaneously, they compete for processing resources with real-time events, such as password changes.
To mitigate performance impact and ensure password synchronization remains responsive, follow these best practices for bulk load operations:
1. Optimize Batch Size
Large bulk load files can cause tasks to become "stuck in progress."
2. Schedule During Off-Peak Hours
Perform bulk load operations during maintenance windows or off-peak hours when user activity (and therefore password change requests) is at its lowest.
3. Monitor the Notification Queue
Monitor the size of the notification queue during the load. If the queue continues to grow without clearing, pause additional loads to allow the system to process the existing backlog before proceeding.