KeyDB
KeyDB copied to clipboard
Snapchat
A Multithreaded Fork of Redis
Hey, I tried to start the docker container for keydb but not matter what I do it doesn't want to start, it always directly stops with no logs or anything....
**Describe the bug** ``` debug.cpp:1138:42: error: no member named '__srr0' in '__darwin_arm_thread_state64' return (void*) uc->uc_mcontext->__ss.__srr0; ~~~~~~~~~~~~~~~~~~~~~ ^ ``` **To reproduce** Follow the steps to build KeyDB **Expected behavior** KeyDB builds...
**Describe the bug** 2024-02-22 keydb-server v6.3.4 started as replica of redis 2024-02-26 promoted to master (by hand - change domain name, set replicaof no one) 2024-05-08 keydb-server just hang, last...
Periodically our KeyDB single instance server is stuck. It works well, but out of the blue under pressure one of its cores is at 100% and clients disconnect with these...
**Describe the bug** I have a keydb cluster with 3 replicas deployed in kubernetes for more than 1 year. Every once in a while it would restart without knowing why...
**The problem/use-case that the feature addresses** Current backup option only supports aws s3, can we please have this feature for gcp gcs also. **Description of the feature** Built in backup...
The last release was in October, it contains issues affecting production. After half a year, the problems have not been fixed and it is unclear whether they will be fixed...
This PR syncs keydb.conf (documentation) file with actual config default for min-clients-per-thread param. See a0abc1eddd071f984950ad8918fad0259c495184 _I'am not sure if right target branch is unstable or main_
