Change Auditor Coordinator (ChangeAuditor.Service) engine uses all available memory, locks server, or is stuck in initializing (4362764)

When starting the Change Auditor Coordinator (ChangeAuditor.Service) engine it uses all available memory, appears to lock the  server or is stuck in initializing.

After reviewing the logs you determine that the coordinator is processing a large number of backlog events.  These events will be loaded into memory prior to processing possibly consuming all available memory.  Review of the ChangeAuditorServiceLog.nptlog shows a large number of entries:

2017-11-10 13:30:19.693 [8][INFO][ChangeAuditor.Sys.HPSqlSchedulerSupervisor.ReplayLogs(0)] Log file C:\ProgramData\Quest\ChangeAuditor\tx2_636137521932057940.txlog replayed successfully

2017-11-10 13:30:19.833 [8][INFO][ChangeAuditor.Sys.HPSqlSchedulerSupervisor.ReplayLogs(0)] Replaying log file C:\ProgramData\Quest\ChangeAuditor\tx2_636137553861923292.txlog

Ensure the coordinator has sufficient resources to process the backlog.  Allow sufficient time for the coordinator to process the events and return to normal operation. See Coordinator requirements