adiholden
adiholden
@dranikpg true this is the same flow as now and for global commands there is no ooo execution
@romange The changes are in main branch with flag to disable/enable the sync between shards as you suggested. How should we compare the performance? I can use the memtear benchmark...
Hi, @romange @dranikpg I run the following command on my laptop while master and replica using 4 cores each one: memtier_benchmark -c 1 --command "mset __key__ foo __key__ bar "...
Hi @dor132 I see that redis returns in info commandstats the following mertrics calls=XXX,usec=XXX,usec_per_call=XXX currently dragonfly returns only the calls=XXX I think it will be good to add the use...
I dont find from which flow we Call the DFLY THREAD command.. can you share where is this call coming from?
After discussing with @ashotland the stop command will stop all open connections and will reject new connections
In the MVP and the current implementation of replica takover which is soon to be finished master shuts down. The problem is that after it will shut down the systemd...
@royjacobson Note: We will need to support setting this flag from config set command
@XiaooLei by default dragonfly will use filename with timestamp for saving snapshot. If you dont want to have snapshot file per timestamp you can use the flag --dbfilename f.e --filename...