chore(deps): bump redix from 1.6.0 to 1.9.2 in /elixir-orchestration

[dependabot]

Bumps redix from 1.6.0 to 1.9.2.

Changelog

Sourced from redix's changelog.

v1.9.2

• Use "least-busy" routing in Redix.Cluster pools. This is considered a bug fix because "sticky routing" (routing to a pool member based on the caller's PID hash) means potentially sticking with a degraded pool member. If you were relying on connection affinity, please stop. When you need to do things such as CLIENT REPLY OFF, open dedicated connections or use pipelines/transactions.

v1.9.1

• Keep Redix.Cluster node pools when DNS returns a different address or address order for the same hostname. Use all resolved IPv4 and IPv6 addresses to match redirects to known pools, with no DNS lookup in command routing. This results in significant less connection/reconnection churn for setups like AWS ElastiCache in serverless mode.
• Add :changed metadata to [:redix, :cluster, :topology_change]. The event still runs after every successful refresh.
• Node IDs in cluster telemetry now keep hostnames from CLUSTER SLOTS after address mapping, instead of resolved IPs.

v1.9.0

• Add Redix.Cluster.hash_slot/1, which exposes the hashing algorithm used by Redix.Cluster.
• Add :cluster metadata field to connection-specific telemetry events (only if connections are part of a cluster).
• Support for resolving multiple peer addresses from an initial address. Redix now supports two strategies: :system, which tries resolved addresses in the order returned by the system resolver, or :random, which shuffles addresses every time. This comes in conjunction with a new :connect_timeout_allocation option which lets you control how long Redix attempts to connect to each address. This change should improve usage of Redix against some servers, such as AWS ElastiCache in serverless mode.

v1.8.2

• Improve the Redix.Cluster command routing fix from 1.8.1 so that it essentially takes more conditions into consideration, like nodes connections being "stuck" or in a connecting state.

v1.8.1

• Route Redix.Cluster commands around disconnected pool members while another member for the same node remains connected.

v1.8.0

• Introduce the :address_mapper option in Redix.Cluster.

v1.7.0

• Introduce :primary_pool_size and :replica_pool_size options for Redix.Cluster. These let you configure per-node pool size, so that you can increase the Elixir-side concurrency in a Redis Cluster setup. Redis is still single-threaded, so apply this only when it makes sense. Defaults have not changed, so a Redix.Cluster connection started without these explicit options defaults to one connection per primary and one per replica (if :read_from_replicas is set).
• Add a few Redix.Cluster-related telemetry events.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 690a190b-71dc-4288-b29c-51327f2b9fe2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}