Circuit Breaker assertion default behavior changes in Gateway 11.2

Products

• CA API Gateway

Issue/Introduction

After upgrading to Layer7 API Gateway 11.2, the Circuit Breaker assertion may behave differently than in previous versions, particularly when configured with Redis. This article explains the shift from local node state to a distributed state model

Environment

• Layer7 API Gateway 11.2
• Redis (External or Embedded)

Cause

 Beginning with Gateway version 11.1.3, the Circuit Breaker assertion was enhanced to use a Distributed In-Memory Store. In version 11.2, this is the standard behavior when a distributed provider like Redis is configured.

Resolution

The assertion now stores its state in a shared, distributed store instead of locally on each Gateway node. This ensures all Gateway nodes share the same circuit state.

• Fail-Fast Mechanism: When one node detects a failure, all other nodes are immediately aware and stop sending requests to the failed endpoint.
• Percentage Thresholds: Users can now define failure thresholds in percentage points.
• HTTP Filtering: Routing failures can now be filtered by HTTP status codes.

If the original local-only behavior is required, review the assertion properties to ensure the state provider is configured according to your requirements.

For more information, see the Apply Circuit Breaker Assertion documentation.