dragonfly
dragonfly copied to clipboard
A modern replacement for Redis and Memcached
when running `docker run docker.dragonflydb.io/dragonflydb/dragonfly --port=8888` for example, our healthcheck.sh fails because it's hardcoded to check :6379 port locally. To fix it - we should add `netstat` to our docker...
According to our new idea CLUSTER CONFIG command should start migration. Also migration process will start from the source node instead of target as it was before.
**Describe the bug** Tonight we got a crash problem on dragonfly instance. This issue may be related to previously reported issue: https://github.com/dragonflydb/dragonfly/issues/2599 ``` dragonfly-1 | I20240222 00:44:07.197453 13 save_stages_controller.cc:283] Saving...
**Describe the bug** BGSAVE and SAVE commands doesn't return OK until background operation finishes. Redis BGSAVE works this way therefore a management code written for a Redis won't work well...
Currently we use master_id for two purposes: cluster node id generation and as "master id" during the replication. 1. Similarly to Redis, we do not protect slave from accidental data...
An example of that is #2629 which we should have returned `-LOADING` instead of `-ERR`. Find out the rest and fix them. See also: https://github.com/dragonflydb/dragonfly/issues/2617
This happen from time to time in our regression tests. Maybe it's worth looking on why: https://github.com/dragonflydb/dragonfly/actions/runs/7923846274 (not critical happens rarely)