Other Admin

License Usage or duplicate

sgarcia
Explorer

I have a license server where I have two indexer pools A and B configured.

Pool A consists of a cluster of 5 indexers and an average consumption of 500GB.

Pool B consists of 1 indexer and a consumption of 100GB per day.

In pool B, data from an F5 index is forwarded to the indexer in pool A.

My license consumption has increased to over 800GB total consumption. My question is:
Is forwarding data from indexer B to indexer A causing me to consume more license?
Would it help if I change the configuration to a single pool?

 

Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Yes, copying data from one index to another, in the same or different indexer, will consume license (except for sourcetype=stash).

That said, I would expect you to use 600GB of license so the extra 200GB came from somewhere else, probably unexpected data sources.

Use the Monitoring Console to show license usage over time to see when the increase started.  Then split the results by source or sourcetype to see which is responsible for the increase.

---
If this reply helps you, Karma would be appreciated.

sgarcia
Explorer

Thanks for the reply, I will make the corresponding changes so as not to forward the data from one indexer or another different indexer. Now the question is that my license server is living in the heavy Forwarder, can I have license duplication problems?

Regards

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Probably not, but I'm not sure what you mean by "license duplication problems".  An LM will store only one copy of a license.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...