One option is obviously to use shared storage. That's a least desirable option.
If I schedule the search to run tscollect, it will be run on a random search head in the cluster, right?
So another option would be to save the search to all cluster members and then use a cron job on each one to run the search and generate the namespace's tsidx files...?
Is there any other cleaner way to do this?
Hi @responsys_cm !
Sorry you haven't received any answers to your question. I'm sure help is on the way!
But, in the mean time, If you want to try to get some immediate help for your question, you should join the 5000+ Splunk users in our public Slack Community chat. People ask each other for immediate help on there daily. You can share your question/link to your post there to see if anyone can take a stab at it.
You first have to request access through https://splk.it/slack. Fill out the form, and once you receive the approval email from our Community Manager (usually the approval process may take a couple days), you can access Slack.com and ask for help in the #general channel.