redis

Author SHA1 Message Date

Author	SHA1	Message	Date
Harkrishn Patro	ca0b6caeed	Propagate message to a node only if the cluster link is healthy. (#11752 ) Currently while a sharded pubsub message publish tries to propagate the message across the cluster, a NULL check is missing for clusterLink. clusterLink could be NULL if the link is causing memory beyond the set threshold cluster-link-sendbuf-limit and server terminates the link. This change introduces two things: Avoids the engine crashes on the publishing node if a message is tried to be sent to a node and the link is NULL. Adds a debugging tool CLUSTERLINK KILL to terminate the clusterLink between two nodes. (cherry picked from commit `fd3975684a`)	2023-02-28 18:32:34 +02:00
DevineLiu	81e72e8e29	[BUG] Fix announced ports not updating on local node when updated at runtime (#10745 ) The cluster-announce-port/cluster-announce-bus-port/cluster-announce-tls-port should take effect at runtime Co-authored-by: Madelyn Olson <madelyneolson@gmail.com> (cherry picked from commit `25ffa79b64`)	2022-12-12 17:36:34 +02:00
Oran Agra	a2a28b8034	Fix assertion when a key is lazy expired during cluster key migration (#11176 ) Redis 7.0 has #9890 which added an assertion when the propagation queue was not flushed and we got to beforeSleep. But it turns out that when processCommands calls getNodeByQuery and decides to reject the command, it can lead to a key that was lazy expired and is deleted without later flushing the propagation queue. This change prevents lazy expiry from deleting the key at this stage (not as part of a command being processed in `call`) (cherry picked from commit `c789fb0aa7`)	2022-09-21 22:42:01 +03:00

Harkrishn Patro

ca0b6caeed

Propagate message to a node only if the cluster link is healthy. (#11752 )

Currently while a sharded pubsub message publish tries to propagate the message across the cluster, a NULL check is missing for clusterLink. clusterLink could be NULL if the link is causing memory beyond the set threshold cluster-link-sendbuf-limit and server terminates the link.

This change introduces two things:

Avoids the engine crashes on the publishing node if a message is tried to be sent to a node and the link is NULL.
Adds a debugging tool CLUSTERLINK KILL to terminate the clusterLink between two nodes.

(cherry picked from commit fd3975684a)

2023-02-28 18:32:34 +02:00

DevineLiu

81e72e8e29

[BUG] Fix announced ports not updating on local node when updated at runtime (#10745 )

The cluster-announce-port/cluster-announce-bus-port/cluster-announce-tls-port should take effect at runtime

Co-authored-by: Madelyn Olson <madelyneolson@gmail.com>
(cherry picked from commit 25ffa79b64)

2022-12-12 17:36:34 +02:00

Oran Agra

a2a28b8034

Fix assertion when a key is lazy expired during cluster key migration (#11176 )

Redis 7.0 has #9890 which added an assertion when the propagation queue
was not flushed and we got to beforeSleep.
But it turns out that when processCommands calls getNodeByQuery and
decides to reject the command, it can lead to a key that was lazy
expired and is deleted without later flushing the propagation queue.

This change prevents lazy expiry from deleting the key at this stage
(not as part of a command being processed in `call`)

(cherry picked from commit c789fb0aa7)

2022-09-21 22:42:01 +03:00

3 Commits