From 0eac6c1d9f388797e127bbb8c30f767202472b9a Mon Sep 17 00:00:00 2001 From: Mark Paluch Date: Wed, 30 Oct 2019 12:21:04 +0100 Subject: [PATCH] =?UTF-8?q?Add=20warning=20log=20if=20MasterReplica(?= =?UTF-8?q?=E2=80=A6,=20Iterable)=20contains=20multiple=20Sentin?= =?UTF-8?q?el=20URIs=20#1165?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../core/masterreplica/MasterReplica.java | 40 +++++++----- .../lettuce/core/masterslave/MasterSlave.java | 63 ++++++++++++------- 2 files changed, 65 insertions(+), 38 deletions(-) diff --git a/src/main/java/io/lettuce/core/masterreplica/MasterReplica.java b/src/main/java/io/lettuce/core/masterreplica/MasterReplica.java index 73ed07462f..659dc285a7 100644 --- a/src/main/java/io/lettuce/core/masterreplica/MasterReplica.java +++ b/src/main/java/io/lettuce/core/masterreplica/MasterReplica.java @@ -49,18 +49,19 @@ * Master-Replica topologies are either static or semi-static. Redis Standalone instances with attached replicas provide no * failover/HA mechanism. Redis Sentinel managed instances are controlled by Redis Sentinel and allow failover (which include * master promotion). The {@link MasterReplica} API supports both mechanisms. The topology is provided by a - * {@link TopologyProvider}: + * {@link io.lettuce.core.masterslave.TopologyProvider}: * * * *

Topology Updates

@@ -69,9 +70,8 @@ *
  • Redis Sentinel: Subscribes to all Sentinels and listens for Pub/Sub messages to trigger topology refreshing
  • * * - *

    Connection Fault-Tolerance

    - * Connecting to Master/Replica bears the possibility that individual nodes are not reachable. {@link MasterReplica} can still - * connect to a partially-available set of nodes. + *

    Connection Fault-Tolerance

    Connecting to Master/Replica bears the possibility that individual nodes are not + * reachable. {@link MasterReplica} can still connect to a partially-available set of nodes. * *