We've been chugging along fine with our 4 unreplicated indexers. I'd like to add a new index now, but have gotten stuck.
This app is successfully deployed from the deployment server:
/opt/splunkforwarder/etc/apps/throwaway_app/
cat /opt/splunkforwarder/etc/apps/throwaway_app/bin/inputs.conf
[script:///opt/splunkforwarder/etc/apps/throwaway_app/bin/topn1.sh]
disabled = false
index = throwaway
# Run every 15 minutes
interval = 900
source = throwaway_top
sourcetype = script:///opt/splunkforwarder/etc/apps/throwaway_app/bin/topn1.sh
[monitor:///opt/logfile.log]
index = throwaway
disabled = false
sourcetype = throwaway.logfile
cat /opt/splunkforwarder/etc/apps/throwaway_app/bin/topn1.sh
#!/bin/bash
#top -n 1 | grep splun[k] | awk '{print $3" "$6" "$7}'
ps -ef
This is added to the end of a well used indexes.conf file and is successfully deployed to the indexers:
[throwaway]
homePath = volume:primary/throwaway
coldPath = volume:primary/throwaway/colddb
thawedPath = $SPLUNK_DB/throwaway/thaweddb
tstatsHomePath = volume:primary/throwaway/datamodel_summary
summaryHomePath = volume:primary/throwaway/summary
maxMemMB = 20
maxHotBuckets = 10
maxConcurrentOptimizes = 6
maxTotalDataSizeMB = 4294967295
maxWarmDBCount = 9999999
maxDataSize = auto_high_volume
The throwaway index is recognized and listed in this search with the settings I have put in indexes.conf
| eventcount summarize=false index=* | dedup index | fields index
As mentioned above, data is not aggregating in the new index either when I search or when I look fora folder. I thought that new data would force the creation of the index folder structure, but nothing is getting created. I may be under the false impression that since we are not replicating data we are not using a master.
I've been reading through the docs, but everything seems to point to clustered (replicated?) indexers, which I don't have. Can someone help?
... View more