Hello there,
We have a Search Head Cluster in 6.5.3 which configured by default in "member by member".
Our configuration :
shc_role_quota_enforcement="0"
shc_local_quota_check="1"
Splunk Documentation :
To enforce quotas on a member-by-member basis, use this configuration:
shc_role_quota_enforcement=false
shc_local_quota_check=true
Version Default enforcement
6.3-6.4 cluster-wide
6.5+ member-by-member
However, while investigating skip ratio, it appears that logs are saying the opposite :
index=_internal sourcetype=scheduler status=skipped | stats count by concurrency_context
cluster-wide 1636
saved-search_cluster-wide 144
Does anyone knows if this is a logging issue or else ?
Thanks for any hint!
↧