John Sully
John Sully
The best way to work around this if you are primarily a windows shop is to run Linux+KeyDB in a HyperV VM. We also have an AMI coming soon for...
Progress is actually being made here. I’ve got initial support for forkless background saving working which is the primary blocker. There is still a *lot* of work to bring up...
Hi @Qix-, Forkless background saving is really about Linux performance first and foremost. The issue with using fork() for snapshotting is write amplification, if you modify even one byte on...
SO_REUSEPORT use to be mandatory for multi-threading to work at all. In more recent builds if you remove this flag then we will only accept new connections on the main...
@ieslv Yes its annoying a more advanced "down detection" is needed with HAProxy. We don't know in advance if a connection will be from a replica so we can't refuse...
The bash variable name needs to keep with the coding standards used elsewhere (all uppercase). Otherwise great change.
@hellojaewon conflicts are resolved per key not per server. What happens when they resync is the timestamp of the last write to the key will be compared and the most...
Seems like a good idea, ben owns the docker image.
Do you have an example case where the original code fails? Or if this is porting from Redis the commit that changed it is sufficient.
Yes it looks like we're missing the tests too