Our app uses an accelerated data model for all searches, which works really well.
I recently stumbled about a discrepancy which I cannot explain. The Data Models UI always shows the acceleration status as 100% completed, and the field Updated is always within a few seconds of the current time. That is good, of course, however when looking at how often populating searches are actually run, things seem to be different. In scheduler.log nearly all searches of type datamodel_acceleration have a status of skipped.
When I visualize how often populating searchs for a specific data model object are run successfully, I get only one successful search every 20 minutes:
My question is: how can the data model be 100% complete (and dashboards always show current data) when populating searches only run once every 20 minutes?
I have observed this on Splunk Enterprise 6.5.3 on Windows (simple single-instance Splunk environment).
Update 2017-06-15: I tested Splunk Enterprise 6.6.0 on Linux and Splunk Enterprise 6.6.1 on Windows. The issue occurs on those versions & platforms, too.
... View more