Requests to the ContextStoreRest interface is throttled in the following scenarios:
-
Service instance is throttled when request rate on node exceeds threshold or Cluster is throttled when request rate for whole cluster exceeds threshold. Check the following applicable threshold configurations:
-
CS Threshold: Instance High Requests per Second
-
CS Threshold: Instance Low Requests per Second
-
CS Threshold: Service High Requests per Second
-
CS Threshold: Service Low Requests per Second
-
Request error rate exceeds the configured threshold. Check the following applicable threshold configurations:
-
Authorization token provided in request header is not valid (ContextStoreRest is integrated with Breeze Authorization service).
-
More than one node is disconnected from the cluster and the "Cluster Deny Service on two node outage" geo-related attribute is enabled.
Note:
If a cluster in a geo-redundant deployment must be restarted, it is recommended that the “Cluster Deny Service on two node outage” attribute is disabled before the restart and then re-enabled afterwards. If this ‘two node outage’ check is executed before the other nodes have started up and joined the cluster – this will trigger throttling on the cluster.
