Roman Gershman
Roman Gershman
Can we close it @abhijat ?
I think there is still work that needs to be done. In any case, I suggest checking how it will fit once you integreate `OnRecv` and be able to offload/load...
requires rebase
@arkorwan thanks for reporting this but we have not succeeded reproducing this last time we checked. Please provide exact docker-compose setup of your master/replica setup, memtier commands with the instructions...
Also can you try running it on 1.27.2 and tell us if it reproduces there?
I suspect that this PR is the reason (https://github.com/dragonflydb/dragonfly/pull/3084/files) - it fixes the bug with memory blowout but lets first focus on reproducing it.
if you can reproduce it with memtier_benchmark it will be great 🙏🏼
thanks - we will follow up on this! so with SETs only it will have the biggest drop, right? can you please repeat the SETs benchmark but with differrent key...
i reproduced it using the following sequence: 1. run both binaries locally `./dragonfly --proactor_threads=4 --dbfilename= ` with replica on port 6380 2. on master: `select 1` and then `debug populate...
same view but with `rate` 🤦🏼 