This issue happens when incoming thruput for hotbuckets is faster than splunk optimize can merge tsidx files and keep the count < 100(hardcoded). If number of tsidx files per hotbucket are >=100, then indexer will apply indexing pause to allow splunk-optimize catch up.
Post 7.2 onwards following config should fix the issue
In indexes.conf set
[default]
maxRunningProcessGroups=12
processTrackerServiceInterval=0
Update (11/16/2022) If the issue is still not resolved, increase maxRunningProcessGroups setting.
For future splunk 9.1 release and splunk cloud releases, the workaround is not needed as the issue is fixed now.
Post 7.2 onwards following config should fix the issue
In indexes.conf set
[default]
maxRunningProcessGroups=12
processTrackerServiceInterval=0
Update (11/16/2022) If the issue is still not resolved, increase maxRunningProcessGroups setting.
For future splunk 9.1 release and splunk cloud releases, the workaround is not needed as the issue is fixed now.