Skip to content

Conversation

sjpotter
Copy link
Contributor

@sjpotter sjpotter commented Dec 5, 2023

Description

Describe your pull request here

An object that provides a managed client for accessing Redis clusters built around the Redis Sentinel protocol.

Checklist

  • Does npm test pass with this change (including linting)?
  • Is the new or changed code fully tested?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

@sjpotter sjpotter requested review from chayim and leibale December 5, 2023 15:39
	returned by aquire()
	used by function passed to use()
- improve steady state waiting between tests
- get masternode from client, not from sentinels themselves (not consistent and then client isn't changing as we expect
- provide extensive logging/tracing on test errors
	- provide a very low impact tracing mechanism withinthe code that only really impacts code when tracing is in use.
- harden testing
	- don't use sentinel[0] for debug error dump as could be downed by a test
	- increase time for sentinel down test to 30s (caused a long taking failover)
- add client-error even / don't pass throuh client errors as errors option for pubsub proxy
- when passing through cient errors as error events, dont pass the event, but the Error object, as only Error objects are supposed to be on 'error'
	-
@leibale leibale linked an issue Feb 5, 2024 that may be closed by this pull request
@leibale leibale marked this pull request as ready for review February 5, 2024 14:47
@leibale leibale merged commit 8f3a276 into redis:v5 Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for Sentinel and RE Discovery Service

2 participants