Backend Throttling and Burst Control Limits Not Working as Expected with Distributed Counter When Connection to Redis Cache Server Is Lost

[sajith-madhusanka]

Description

When connectivity with the Redis cache server is lost, the choreo connect fails to throttle the requests. Instead, it returns the following error message and a 500 HTTP status code.

{"description":"Error during validating the request","message":"Unclassified Validation Failure","code":"102500"}

Steps to Reproduce

• Deploy the choreo connect with the APIM.
• Configure the Redis cache server with the choreo connect enforcer.
• Deploy a sample API via the publisher portal.
• Configure the max backend throughput as 100 TPS
• Conduct a load test using the Jmeter client
  • Test Duration: 5 mins
  • Single thread group Invoke single API.
• Breaks the Redis cache server connectivity after 3 minutes (undeploy the Redis Cache Server node)

Version

1.0.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response