8ae626508b
- Bug Fixes - Core
* Fix typo in REGISTER_API macro to prevent segfaults when loading Redis
modules (#608)
* Fix the command duration reset issue when clients are blocked and commands
are reprocessed (#526)
* Fix the data type conversion error in zrangeResultBeginStore (Redis#13148)
* Fix a crash caused by quicklist node merges (Redis#13040)
* Fix crashes in module blocking client timeout cases (Redis#13011)
* Fix conversion of numbers in Lua args to Redis args
(Redis#13115, Fixes Redis#13113)
* Fix crash in LSET command when replacing small list items with larger ones,
creating listpacks larger than 4GB (Redis#12955, Fixes Redis#12864)
* Fix blocking command timeout reset issue during reprocessing (Redis#13004)
- Bug Fixes - Cluster
* Fix the CLUSTER SHARDS command to display accurate slot information even
if a primary node fails (#790, Fixes #784)
* Fix an issue where module authentication failed when the cluster was down
(#693, Fixes #619)
* Ensure only primary nodes with slots can mark another node as failed (#634)
* Improve MEET command reliability under link failures to maintain cluster
membership symmetry (#461)
* Allow single primary node to mark potentially failed replica as FAIL in
single-shard cluster (Redis#12824)
- Bug Fixes - Sentinel
* Accept redis-sentinel to start Valkey in sentinel mode (#731, Fixes #719)
- Bug Fixes - CLI
* Ensure the --count option in redis-cli works correctly even without
--pattern (Redis#13092)
* Fix redis-check-aof misidentifying data in manifest format as MP-AOF
OBS-URL: https://build.opensuse.org/package/show/server:database/valkey?expand=0&rev=13
README.SUSE ------------- Valkey Server ============== 1. cp -a /etc/valkey/default.conf.example /etc/valkey/instancename.conf We use the "cp -a" here, so that our permissions are preserved. In case you copied the file with out the "-a" chown root:valkey /etc/valkey/instancename.conf chmod u=rw,g=r,o= /etc/valkey/instancename.conf 2. change at least pidfile, logfile and dir setting # the pid file *has* to match your config filename without the ".conf" pidfile /run/valkey/instancename.pid logfile /var/log/valkey/instancename.log dir /var/lib/valkey/instancename/ If you want to run more than one instance you also have to change the socket path and/or the ip:port combination. e.g. /run/valkey/instancename.sock Also make sure if you copy configurations from somewhere, that "daemonize" should be set to "no". 3. create the database dir: $ install -d -o valkey -g valkey -m 0750 /var/lib/valkey/instancename/ 4. systemctl start valkey@instancename 5. systemctl enable valkey@instancename 6. To stop/restart all instances at the same time use: systemctl restart valkey.target systemctl stop valkey.target Valkey Sentinel ================ 1. cp -a /etc/valkey/sentinel.conf.example /etc/valkey/sentinel-instancename.conf We use the "cp -a" here, so that our permissions are preserved. In case you copied the file with out the "-a" chown root:valkey /etc/valkey/sentinel-instancename.conf chmod u=rw,g=rw,o= /etc/valkey/sentinel-instancename.conf Please note that the sentinel config needs write permissions for the group. The chmod line differs from the line for the normal valkey server. 2. change at least pidfile, logfile setting # the pid file *has* to match your config filename without the ".conf" pidfile /run/valkey/instancename.pid logfile /var/log/valkey/instancename.log If you want to run more than one instance you also have to change the socket path and/or the ip:port combination. e.g. /run/valkey/instancename.sock Also make sure if you copy configurations from somewhere, that "daemonize" should be set to "no". 4. systemctl start valkey-sentinel@instancename 5. systemctl enable valkey-sentinel@instancename 6. To stop/restart all instances at the same time use: systemctl restart valkey-sentinel.target systemctl stop valkey-sentinel.target Integration with apache when using unix domain sockets ========================================================= If you plan to use valkey in combination with apache, then you should add 'valkey' to apache group and set 'unixsocketperm 770': $ usermod -a -G valkey wwwrun $ systemctl restart apache2 then apache is able to connect to valkey socket Migrating from Redis ======================= Migrating from Redis to Valkey is simple to execute. Just install "valkey-compat-redis" package. The scriptlet should automatically take care of the necessary transitions.