Installation

Creating multiple license pools

Contributor

What is the primary advantage of having multiple license pools ?

1.If i do not have license pool also i can point any number of slaves to the default pool and index the data.
2.When i have multiple pools and say limit the size of a pool to low volume. Once the volume is reached license warnings will be thrown. No one wants this scenario.
3.Does this have any performance boost?
4.What kind of differentiation I am benefited by this license pool concept ?

Tags (2)
1 Solution

SplunkTrust
SplunkTrust

Hi chimbudp,

the main purpose for License pools is that you can define a pool of license volume from a given license license stack and specify other indexing Splunk instances as members of that pool for the purposes of volume usage and tracking. Let's say you have three departments A, B & C all together provide some money to buy the license, but C provides to most. So you create a larger pool only for C and the rest for A & B.

This is only a basic example but it shows how you can use license pooling.

Following the answers to your questions:

  1. you can as well allow any indexer to use any license pool.
  2. you're right nobody wants that. But on the other the would be a reason to limit the size of the pool so this would be a good way to 'force' people to keep the data usage low.
  3. no license pooling does not have any performance impact.
  4. see the example at the top

Just in case you havn't read it already, here is the docs about License Groups,stacks & pools

hope this helps ...

cheers, MuS

View solution in original post

SplunkTrust
SplunkTrust

Hi chimbudp,

the main purpose for License pools is that you can define a pool of license volume from a given license license stack and specify other indexing Splunk instances as members of that pool for the purposes of volume usage and tracking. Let's say you have three departments A, B & C all together provide some money to buy the license, but C provides to most. So you create a larger pool only for C and the rest for A & B.

This is only a basic example but it shows how you can use license pooling.

Following the answers to your questions:

  1. you can as well allow any indexer to use any license pool.
  2. you're right nobody wants that. But on the other the would be a reason to limit the size of the pool so this would be a good way to 'force' people to keep the data usage low.
  3. no license pooling does not have any performance impact.
  4. see the example at the top

Just in case you havn't read it already, here is the docs about License Groups,stacks & pools

hope this helps ...

cheers, MuS

View solution in original post