* fix: recycle connections in some Redis Cluster scenarios
This issue was surfaced in a Cloud Provider solution that used for
rolling out new nodes using the same address (hostname) of the nodes
that will be replaced in a Redis Cluster, while the former ones once
depromoted as Slaves would continue in service during some mintues
for redirecting traffic.
The solution basically identifies when the connection could be stale
since a MOVED response will be returned using the same address (hostname)
that is being used by the connection. At that moment we consider the
connection as no longer usable forcing to recycle the connection.
* Remove OpenTelemetry from the code (but leave redisotel as is) (#1782)
* Add XAutoClaim command (#1780)
* fix typo (#1788)
* xgroup/xadd/xtrim supports new options (#1787)
* support cmd option
XGROUP CREATECONSUMER
XTRIM MINID LIMIT
XADD NOMKSTREAM MINID LIMIT
Signed-off-by: monkey <golang@88.com>
* add XAddArgs.Approx doc
Signed-off-by: monkey92t <golang@88.com>
* Add Bun to readme
* Upgrade the <sorted set> series of commands (#1792)
* Upgrade the <sorted set> series of commands
Signed-off-by: monkey92t <golang@88.com>
* Cancel the Deprecated mark of ZAddNX and ZAddXX
Signed-off-by: monkey92t <golang@88.com>
* Explain the use restrictions of KeepTTL. (#1799)
Signed-off-by: monkey92t <golang@88.com>
* Adjust KeepTTL annotation.
Signed-off-by: monkey92t <golang@88.com>
* the hello command throws possible errors, It may affect the "read timeout" test result.
Signed-off-by: monkey92t <golang@88.com>
Co-authored-by: Vladimir Mihailenco <vladimir.webdev@gmail.com>
Co-authored-by: ericmillin <31105612+ericmillin@users.noreply.github.com>
Co-authored-by: heyanfu <1145291570@qq.com>
