In the Pega helm charts, there is a parameter to enable latency aware policy:

  # Enable a latency awareness policy, which collects the latencies of the queries for each Cassandra node and maintains   # a per-node latency score (an average).   # latencyAwarePolicy: false

According to the Datastax docs:

When used, this policy will collect the latencies of the queries to each Cassandra node and maintain a per-node latency score (an average). Based on these scores, the policy will penalize (technically, it will ignore them unless no other nodes are up) the nodes that are slower than the best performing node by more than some configurable amount (the exclusion threshold).

Once a node is excluded from query plans (because its averaged latency grew over the exclusion threshold), its latency score will not be updated anymore (since it is not queried). To give a chance to this node to recover, the policy has a configurable retry period. The policy will not penalize a host for which no measurement has been collected for more than this retry period.

What is the configurable exclusion threshold set to?

What is the configurable retry period set to?

Since there are no parameters for these, can it be assumed that these are already set by Pega?