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.

Comments (0) New comment

innaman Rank: 646

Asked 2 years ago

Answer this question Follow

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.

Comments (7) New comment

by innaman Rank: 646 on 5/8/2018 8:28:45 PM | Like (0) | Report

Thanks Stefan for the info.

The system version is 6.0.3.

What would be the basic history limit for this version, we are working on data center projects where huge number of logs have to be historised. This info would be really helpful in deciding the logs, and dividing among connectivity servers for future projects, apart from the limitation set in standard manual, I believe 10000 is the limit set for each CS.

by Stefan Stromqvist AKS expert

Rank: 1 on 5/8/2018 9:28:32 PM | Like (0) | Report

There are too many variables to be able to put a single integer (no of logs) as the only limitation.

- no of primary logs
- no of secondary logs
- sample interval of logs
- length of logs
- CPU power available
- disk throughput available
- total diskspace used by Basic History

All together these form some kind of KPIs for Basic History. There could be additional factors that needs to be weighed in.

What are your figures?

by innaman Rank: 646 on 5/9/2018 1:11:38 AM | Like (0) | Report

Here is the rough estimation:

Number of primary logs : 30,000
Number of Secondary Logs : 0
Sample interval : 30Sec average
Length of logs: 50 days
CPU power available : 3.Ghz, with 4 virtual processors
Disk space used by Basic History: 45 GB

Do we have any standard tool to calculate the maximum capacity, with these figures?

Thanks,
Narasimha

by innaman Rank: 646 on 5/9/2018 1:12:19 AM | Like (0) | Report

No secondary logs, because we have 800xA History.

by innaman Rank: 646 on 5/9/2018 1:13:41 AM | Like (0) | Report

By the way, the secondary service is running now.

We are facing the initialize and ready state on primary server now.

by innaman Rank: 646 on 5/9/2018 1:24:04 AM | Like (0) | Report

Sorry to bother you with my queries: Last one for now:

Is this Basic history service goes to next stage after each restart? I mean whenever it cannot complete the sync within 5 mins, it restarts. But, next sync will start from beginning or it will have a track of completed sync and move on to next.
The reason why this question is, if it moves to next stage, I can leave the system overnight and can continue tomorrow in the hope that it will sync at the end, else I have to rise a support case to bring the service

by Stefan Stromqvist AKS expert

Rank: 1 on 5/9/2018 1:43:14 AM | Like (0) | Report

30.000 logs in one Basic History service provider?

Or 3 pairs of CS each with 10.000 logs?

If I read the system guide correct, the limit is 20.000 logs per connectivity server. This limit was in v5.1 10.000. I believe the limit was raised with 6.0 given that Basic History is compiled for Large Address Aware (fake 64-bit).

I recommend staying below 20.000 logs per server node.

Remember, a system with separated AS and CS allows for this configuration (even though it is not mentioned)

AS1/AS2: Basic History service group A
CS1/CS2: Basic History service group B

2 service groups á 20.000 logs = 40.000 logs.

History Source is the aspect controlling whether a branch is logged by group A or group B.

Also, please check System Event List and Basic History service virtual bytes (with perfmon.exe).

Add new comment

Stefan Stromqvist AKS expert

Rank: 1

Answered 2 years ago

Question details

Basic History service is toggling between "Initialise" and "Ready" state

Voted best answer

Other questions needing answers

Related topics

Related content

AKS experts