Reporting

Datamodel acceleration broken after adding fields - "cannot use search for missing acceleration data"

rmdfrb
Explorer

I modified the Splunk_SA_CIM Authentication data model to include some extra fields (account domains), and after re-enabling acceleration I get the follwing error:

The search for datamodel
'Authentication' failed to parse,
cannot use search for missing
acceleration data

I presume this means that the old TSIDX files are still sitting around but contain a different set of fields than are expected. I was under the impression that Splunk knew how to clean these up on its own (or at least clean things up after they age out of the summary range), but that is apparently not happening. Any ideas what has gone wrong? What would be the best way to clean up this mess in a distributed environment?

Thanks!

dmaislin_splunk
Splunk Employee
Splunk Employee

Remove any macro definitions from your data models and expand them. It will work fine after that.

0 Karma

m4him7
Path Finder

I am having the same issue. Did you find the solution?

0 Karma

dmaislin_splunk
Splunk Employee
Splunk Employee

Remove any macro definitions from your data models and expand them. It will work fine after that.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Fuel Your Journey: What’s Waiting for You at the .conf26 Acceleration Station

Navigating the show floor at .conf26 isn't just about keynotes and technical breakout sessions; it's also ...

Join the Final Session of the Data Management & Federation Bootcamp Series

Over the past three sessions of the Data Management & Federation Bootcamp Series, we've explored how to build ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...