Splunk® Enterprise

Workload Management

Configure workload management on distributed deployments

You can use workload management to allocate resources in both non-clustered and clustered (distributed) search environments.

The resource allocation for workload categories and workload pools can be different on search heads and indexers.

Configure workload management on non-clustered indexers

To configure workload management on non-clustered indexers, you must first configure and enable workload management on the search head, then copy the enabled workload_pools.conf file to all indexers.

You do not need to copy workload_rules.conf to indexers. Its functionality applies to search heads only.

To configure and enable workload management on non-clustered indexers:

  1. Configure and enable workload management on the search head. See Configure workload management.
  2. Copy the enabled workload_pools.conf file to all indexers.
  3. Reload workload_pools.conf on each indexer. For example:
    curl -k -u admin:pass https://<host>:<mPort>/services/configs/services/workloads/pools/_reload
    

    Reloading workload_pools.conf enables workload management.

Configure workload management on an indexer cluster

To configure workload management on an indexer cluster, you must first configure and enable workload management on the search head, then use the configuration bundle method to push workload_pools.conf from the cluster manager node to peer nodes.

You do not need to push workload_rules.conf to the indexer cluster. Its functionality applies to search heads only.

To configure and enable workload management on an indexer cluster:

  1. Configure and enable workload management on the search head. See Configure workload management.
  2. Copy the enabled workload_pools.conf file from the search head to the configuration bundle on the cluster manager node.
  3. Distribute the configuration bundle to all peer nodes. For detailed instructions, see Distribute the configuration bundle.
    After the bundle push, peer nodes automatically reload the enabled configuration file, which enables workload management.

Configure workload management on a search head cluster

Automatic configuration replication is used to distribute workload management configuration files to all search head cluster members.

Both workload_pools.conf and workload_rules.conf are required on all search heads.

To configure workload management on a search head cluster using the configuration replication method:

  1. On any cluster member, in Splunk Web, click Settings > Workload Management.
  2. Configure and enable workload management. See Configure workload management.
    The search head cluster automatically replicates the configuration to all cluster members. This triggers a reload of the enabled configuration files on each cluster member, which enables workload management.

For more information on configuration replication, see Configuration updates the cluster replicates.

You can use the deployer bundle push method to distribute workload management configuration files to search head cluster members. However, you cannot use both the deployer bundle push method and the configuration replication method to update cluster configurations. You must choose one method and use only that method. Using both methods can cause workload management to fail. For more information, see Use the deployer to distribute apps and configuration updates.

Last modified on 23 October, 2023
Configure admission rules to prefilter searches   Set access controls for workload management

This documentation applies to the following versions of Splunk® Enterprise: 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.3.0, 9.3.1


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters