Basic History service is toggling between "Initialise" and "Ready" state
Hi,
We have redundant connectivity servers with around 10000 basic history logs configured.
Today i had restarted the secondary connectivity server (CS) while updating the history software to RU2, after the restart the basic History service is not reaching service state. It is continuously toggling between the "Initialise" and "Ready" state.
1. Restarted the CS, no luck.
2. I have disabled the service and renamed the history folder (from C:\OperatorITData\History\{****}\, then started the service, so new history folder has been created copied synched from primary connectivity server, but still the service is toggling.
Please let me know if any workaround to stabilise this service.
Voted best answer
What version?
Before 5.1 RevD RU5 Basic History was limited to 32-bit memory space.
On 32-bit, 10.000 logs is a lot and could overshoot what is possible to log if the sample intervals are fast and retention time is long. As a rule of thumb, keep history disk usage below 50 GB when on 32-bit.
Also, too many secondary logs may cause excessive memory usage. Keep log hierarchy "reasonable", e.g. 1sec/1week (raw) --> 1min/1month (TimeAverage) --> 10min/1year (TimeAverage)
Suggest adding a Windows Performance Monitor counter log for AdvHtHistorySrv.exe and Virtual Bytes. The counter must not shoot up to 2GB...
Wiping the data folder will cause new empty logs to be created, if the size is large the log synchronization may take a significant time to perform as the pace is intentionally slow. To speed up sync, copy the folder from the peer instead - then the sync operation will complete in much less time.
Add new comment