🐛 fix: Redis Cluster Bug + 🧪 Enhance Test Coverage (#10518)
Some checks are pending
Docker Dev Branch Images Build / build (Dockerfile, lc-dev, node) (push) Waiting to run
Docker Dev Branch Images Build / build (Dockerfile.multi, lc-dev-api, api-build) (push) Waiting to run

*  feat: Implement scanIterator method for Redis cluster client
This resolves the bug where `ServerConfigsCacheRedis#getAll` returns an empty object when a Redis Cluster (instead of a single node server is used)

*  feat: Update cache integration tests for Redis cluster support
This commit is contained in:
Theo N. Truong 2025-11-16 09:58:52 -07:00 committed by GitHub
parent f228f2a91d
commit 8c531b921e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
14 changed files with 81 additions and 134 deletions

View file

@ -25,10 +25,8 @@ describe('LeaderElection with Redis', () => {
throw new Error('Redis client is not initialized');
}
// Wait for Redis to be ready
if (!keyvRedisClient.isOpen) {
await keyvRedisClient.connect();
}
// Wait for connection and topology discovery to complete
await redisClients.keyvRedisClientReady;
// Increase max listeners to handle many instances in tests
process.setMaxListeners(200);