Reference: https://wiki.splunk.com/Deploy:BucketRotationAndRetention

Reference:https://docs.splunk.com/Documentation/Forwarder/8.2.1/Forwarder/Configureloadbalancing

https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Protectagainstlossofin-flightdata#:~:
text=The%20default%20for%20the%20maxQueueSize,wait%20queue%20size%20is%2021MB.
https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Protectagainstlossofin-flightdata

Using the Splunk reference URL https://docs.splunk.com/Splexicon:Searchpeer
"search peer is a splunk platform instance that responds to search requests from a search head. The term
"search peer" is usally synonymous with the indexer role in a distributed search topology. However, other instance types also have access to indexed data, particularly internal diagnostic data, and thus function as search peers when they respond to search requests for that data."

In Splunk Enterprise, when you configure the server.conf file with strict pool quota=false, it means that license pools are allowed to share the total available license quota rather than being restricted to their individually allocated quotas. However, this does not prevent pools from issuing warnings if they exceed their allocated limits.
Given the environment with a 1000 GB/day license split into three pools:
Pool X: 500 GB/day license, 100 GB used
Pool Y: 350 GB/day license, 400 GB used
Pool Z: 150 GB/day license, 300 GB used
Let's analyze the usage:
Pool X is allocated 500 GB/day but has only used 100 GB, well within its limit.
Pool Y is allocated 350 GB/day but has used 400 GB, which exceeds its limit by 50 GB.
Pool Z is allocated 150 GB/day but has used 300 GB, which exceeds its limit by 150 GB.
Even with strict pool quota=false, pools Y and Z have exceeded their individual allocated quotas and will issue warnings. Pool X has not exceeded its quota and thus will not issue any warnings. Therefore, the pools that are issued warnings are Y and Z.