Create or edit a license pool
This topic discusses creating a license pool from one or more installed licenses, as well as editing an existing license pool. Before you proceed, you may want to review these topics:
- Read "How Splunk licensing works" in this manual for an introduction to Splunk licensing.
- Read "Groups, stacks, pools, and other terminology" in this manual for more information about Splunk license terms.
- Read "Install a license" to learn more about installing licenses.
- Read "Manage licenses from the CLI" in this manual for help with performing these tasks from the command line.
When you first download and install Splunk, it includes a 500 MB 60 day Enterprise Trial license. This instance of Splunk is automatically configured as a stand-alone license master, and you cannot create a pool or define any license slaves for this type of license. If you want to create one or more stacks or pools and assign multiple indexers to them, you must purchase and install an Enterprise license.
In the following example of Settings > Licensing, a 100 MB Enterprise license has just been installed onto a brand new Splunk installation:
When you install an Enterprise license onto a brand new Splunk server, Splunk automatically creates an Enterprise license stack called Splunk Enterprise Stack from it and defines a default license pool for it called
The default configuration for this default pool adds any license slave that connects to this license master to the pool. You can edit the pool to change this configuration, to add more indexers to it, or create a new license pool from this stack.
To edit an existing license pool
1. Next to the license pool you want to edit, click Edit. The Edit license pool page is displayed.
2. If desired, change the allocation or alter how indexers are permitted to access this pool. You can also change the description, but not the name of the pool.
3. Click Submit.
To create a new license pool
Important: Before you can create a new license pool from the default Enterprise stack, you must make some indexing volume available by either editing the
auto_generated_pool_enterprise pool and reducing its allocation, or deleting the pool entirely. Click Delete next to the pool's name to delete it.
2. Specify a name and optionally, a description for the pool.
3. Set the allocation for this pool. The allocation is how much of the overall stack's licensing volume is available for use by the indexers who belong to this pool. The allocation can be a specific value, or the entire amount of indexing volume available in the stack, as long as it is not allocated to any other pool.
4. Specify how indexers are to access this pool. The options are:
- Any indexer in your environment that is configured as license slave can connect to this license pool and use the license allocation within it.
- Only indexers that you specify can connect to this pool and use the license allocation within it.
5. To allow a specific indexer to draw from the pool, click the plus sign next to the name of the indexer in the list of Available indexers to move it into the list of Associated indexers.
Configure a license slave
Add an indexer to a license pool
This documentation applies to the following versions of Splunk® Enterprise: 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, 6.0.13, 6.0.14, 6.1, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.1.12, 6.1.13, 6.2.0, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.2.12, 6.2.13, 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 7.0.0, 7.0.1