Fixed in 9.0.4 ... View more

Most answers here are from long ago, so I will add this option here as well, that will work on more modern versions of RHEL based systems that run tuned version 2.11 and above. The easiest way I found to disable THP is using tuned.   mkdir /etc/tuned/splunk_idx cat << EOF > /etc/tuned/splunk_idx/tuned.conf # # tuned configuration # [main] summary=Optimize for Splunk Indexer description=Configures THP for better Splunk performance include=latency-performance [vm] transparent_hugepages=never transparent_hugepage.defrag=never EOF tuned-adm profile splunk_idx   I tested this on RHEL/CentOS version 7.8+ and it works fine. ... View more

services started with the legacy init system, do not honor limits.conf, since it comes up right in the beginning of the system startup, before it reads the limits and pam. As other mentioned, use systemd to start the service, and you can add it in the unit file ... View more

You can only back up warm or cold buckets. Here is a quick and dirty way to do it: If you are running Linux, this will copy all non-hot buckets created in the last day to /tmp. replace /tmp with you desired target directory warm_buckets=$(find /opt/splunk/var/lib/splunk -mmin -1440 -type d -name "db_*") for i in $warm_buckets; do mkdir -p /tmp/$i/rawdata; done for i in $warm_buckets; do rsync -auvn "$i"/*/journal.gz /tmp$i; done   Hope this helps ... View more

That means Splunk is not running. start Splunk in debug mode $SPLUNK_HOME/bin/splunk start --debug ... View more

There are several ways you can see if there is data in a specific index. You can try " | dbinspect index=<your_index> ", or "|tstats count where index=<your_index> by _time span=1d" ... View more

Sourcetypes do not need to exist on the search head. Does the search return results if you remove everything after the raw search? (from the first pipe, till the end) ... View more

What user are you running Splunk as? ... View more

Do you mean you tell rsyslog to listen on multiple ports, and write data from specific ports to a specific file? If its TCP you should see a connection in  netstat from that host, and you would see what port it's connected to. Or you can use tcpdump to see the traffic. However netstat and tcpdump will not be very useful if you use a load-balancer to send the traffic. In that case, something like ngrep would be more useful. ... View more

According to Splunk support, the add-on does not currently support UCS Central, only UCS Manager. ... View more

Here is the answer I got from support: The app is not compatible with UCS Central, only with the older UCS manager. I posted a ER on ideas to add support for UCS central. You can upvote it here: https://ideas.splunk.com/ideas/APPSID-I-139 ... View more

I have the same issue. ... View more

10Gbe should be more than enough for indexing and searches. If it's not enough, you should probably add more indexers instead of more NIC's. The only reason you should be concerned about throughput is when you're using SmartStore, as the traffic to S3 will increase depending on your setup and search behavior. But with many indexers capable of doing 10Gbs you will probably saturate your uplinks to AWS or your local S3 Storage solution. Also, Splunk will perform a lot better with more but slimmer servers instead of fewer fat servers. Having 10 servers with 128 cores is not the same than 20 servers with 64 cores. More smaller servers = better. ... View more

It will use all throughput the OS makes available to it, be it 1Gbe or 200Gbe ... View more

Had the same problem. Please post your reply as an answer, so people know that it was actually answered. ... View more

Thanks for making me aware of the typo. Fixed. The reason for doing it one at a time, is to minimize the downtime, and a massive cluster-wide bucket fix-up. Taking your time moving them over ensures that the replication factor will remain reasonable and searches will be able to continue, since everyone has a different RF/SF setup. Enabling and disabling maintenance mode will fix up missing buckets after the data move. ... View more

I would not suggest making any changes on a Indexer locally. Here is my suggestion: Lets assume that the original Index is at /opt/splunk/var/lib/splunk/defaultdb , and the new location will be at /splunk/defaultdb . In order to limit the down-time of each indexer to the minimum, we will do it in a few steps. First, while the service is still running, rsync the data from the old location to the new one: Note: When running the rsync command, use a trailing slash only after the source path, and not after the destination path. rsync -auv /opt/splunk/var/lib/splunk/defaultdb/ /splunk/defaultdb . This will create an initial copy of the data to the new location. The initial sync may take some time, depending on the size of your data, there also may be a lot of changes to the data when that process is done due to bucket rolling from hot/warm/cold. Now we want to do another rsync to send the recent changes, this will be a lot faster. But now we will add the --delete argument, so it deletes rolled buckets from the new location. like so: rsync -auvv --delete /opt/splunk/var/lib/splunk/defaultdb/ /splunk/defaultdb if you want to be able to look at what rsync did, you can send output to a log file by adding the --log-file=/tmp/rsync-`date %s`.out to the command. Put the CM in maintenance mode and stop Splunk, and do the final sync. On the master: $SPLUNK_HOME/bin/splunk enable maintenance-mode --answer-yes On the Indexer: $SPLUNK_HOME/bin/splunk stop Do the final sync: rsync -auvv --delete /opt/splunk/var/lib/splunk/defaultdb/ /splunk/defaultdb Move away the old index data to a backup location: mv /opt/splunk/var/lib/splunk/defaultdb /opt/splunk/var/lib/splunk/OLD.defaultdb Latstly, create a symlink from the new location to the old one: ln -s /splunk/defaultdb /opt/splunk/var/lib/splunk/defaultdb . Now you can start splunk, and not have to mess around with indexes.conf After you start the indexer, make sure that the buckets are visible by check the RF/SF on the CM, after that you can take the cluster out of maintenance mode, to fill in the few buckets that been rolled while that indexer was down. $SPLUNK_HOME/bin/splunk disable maintenance-mode --answer-yes Repeat the same process 1-7 on each indexer in the cluster, one indexer at a time. After doing this on all indexers, you can change the path in indexes.conf on the master, and push out the new bundle. A Indexer restart is required when changing the path of a index, so the master will initiate a restart. After you did all that, and have confirmed that all the buckets are visible in Splunk, you can remove the old data, and delete the symlink: rm -rf /opt/splunk/var/lib/splunk/OLD.defaultdb rm /opt/splunk/var/lib/splunk/defaultdb Please comment if I missed something. I hope this helps. ... View more

Make sure permissions are correct on the destination, use rsync -auv /old/index/dir/ /new/index/dir to preserve the timestamps, permission and ownership, when done rename the old index directory with the mv command, then ln -s /new/index/dir /old/index/dir . Make sure splunk is not running, however you can do an initial rsync while Splunk is up, and when that's sync is done, shut down Splunk, and do the final rsync with the --delete flag. this will delete the files that have disappeared from the index while you were doing the initial sync. I go for the linking route, because I'm clustered, and I don't want to mess around with indexes.conf by changing the location of the indexes. But if you are not clustered, you can just rename the old folder, create a new folder with the same name, then mount the new partition in the same place the old one was, like this: mv /index/folder/location /index/folder/location.OLD mkdir /index/folder/location mount /index/folder/location The last one assuming you put it in fstab. After confirming that everything is in working order, you can delete the old data. ... View more