Reporting

Splunk Datamodel Acceleration just work in the default search group

chanhdai96
Loves-to-Learn Everything

I have 2 server groups on Splunk (dmc_group_1 & dmc_group_2) and "dmc_group_1" is the default search group.
When inspecting the DM acceleration scheduled searches, I found that they only run in peers of default search group and .tsidx files were just generated in this group's indexers, even though the search query contained "splunk_server=*". I don't know why Splunk cannot understand "splunk_server=*" in this case.

INFO  DistributedSearchResultCollectionManager - Default search group:dmc_group_1
INFO  SearchTargeter - Peer NEW-IDX-1 is not in default group dmc_group_1. Not connecting
INFO  DistributedSearchResultCollectionManager - Not connecting to peer 'NEW-IDX-1' because it has been optimized out. 

How can the acceleration scheduled searches run in all search peers without adding "dmc_group_2" to the default group.

Thank you

Labels (3)
Tags (2)
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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...