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
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...