[RELEASE] Redis 6.0.7 is out

274 views
Skip to first unread message

re...@redis.io

unread,
Sep 1, 2020, 9:10:00 AM9/1/20
to redi...@googlegroups.com
Hi friends,

Redis 6.0.7 is out. The main driver for this release a fixes to a couple
of issues
(see the first two listed) that cause protocol errors.

Redis 6.0.7 Released Fri Aug 28 11:05:09 IDT 2020

Upgrade urgency MODERATE: several bugs with moderate impact are fixed.

Bug fixes:
* CONFIG SET could hung the client when arrives during RDB/ROF loading
(When
processed after another command that was also rejected with -LOADING
error)
* LPOS command when RANK is greater than matches responded wiht broken
protocol
(negative multi-bulk count)
* UNLINK / Lazyfree for stream type key would have never do async
freeing
* PERSIST should invalidate WATCH (Like EXPIRE does)
* EXEC with only read commands could have be rejected when OOM
* TLS: relax verification on CONFIG SET (Don't error if some configs are
set
and tls isn't enabled)
* TLS: support cluster/replication without tls-port
* Systemd startup after network is online
* Redis-benchmark improvements
* Various small bug fixes

New features:
* Add oom-score-adj configuration option to control Linux OOM killer
* Show IO threads statistics and status in INFO output
* Add optional tls verification mode (see tls-auth-clients)

Module API:
* Add RedisModule_HoldString
* Add loaded keyspace event
* Fix RedisModuleEvent_LoadingProgress
* Fix RedisModuleEvent_MasterLinkChange hook missing on successful psync
* Fix missing RM_CLIENTINFO_FLAG_SSL
* Refactor redismodule.h for use with -fno-common / extern

Cheers,
Redis team

P.S. Unless the unexpected happens, this should be the last 6.0.x
release. We are now focused on making the first release candidate for
Redis 6.2.

John Fak

unread,
Sep 1, 2020, 10:44:26 AM9/1/20
to redi...@googlegroups.com
Hi all 
I would like to run sentinel on k8 on there own pods.

So clients separate from Sentinel.
Sentinel separate from M/R redis.

Is this possible ?
Does  someone have a sample yaml config file that can be used to configure sentinel against the core kubernetes service  for redis M/S

My service for the redis cluster access is defined as below 

Name:                     redisdev-service
Namespace:                redis-dev
Labels:                   <none>
Selector:                 app=redis-cluster
Type:                     NodePort
IP:                         10.43.223.70
Port:                      <unset>  6379/TCP
TargetPort:               6379/TCP
NodePort:                 <unset>  30007/TCP
Endpoints:                10.42.1.213:6379,10.42.2.65:6379,10.42.5.125:6379 + 3 more...
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>




--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/redis-db/82aee333b507874892c98e357f152f6d%40redis.io.
Reply all
Reply to author
Forward
0 new messages