KB Article #176104

Sentinel takes too long to start with log lines having keyword Max(EVENTID) spanning long time periods

Problem

Sentinel takes too long to start with log lines having keyword Max(EVENTID) spanning long time periods per the example below.

2014-03-23 04:26:42 [FrontEndServer ] WARN  L197  EventIdGeneratorImpl.getLastId - Table HISTORIC_742936568: empty
2014-03-23 05:11:00 [FrontEndServer ] WARN  L203  EventIdGeneratorImpl.getLastId - Table CURRENT_ARHIVED06: Max(EVENTID) = 1934690105215
2014-03-23 06:11:07 [FrontEndServer ] WARN  L203  EventIdGeneratorImpl.getLastId - Table HISTORIC_ARHIVED03: Max(EVENTID) = 7670146983311

Resolution

Avoid use of custom tables starting with prefixes CURRENT or HISTORIC from Sentinel's database schema.

The above resolution brought down the Sentinel startup time for a customer from 14 hours to 2 minutes.

Still need help?

If this information wasn't helpful to you, just drop us a line. We'll get back to you as soon as possible.