hulk
cool, I think we don't need to limit the length of name. We can still use the fixed 40 chars as script key name, and the name if not 40...
@taylorchu Yes, Kvrocks does store and propagate scripts now, what errors you occurred, can you paste the error or reproduce steps?
Oooop, sorry to hear that. We should keep those messages consistent as possible as we can. You can help to submit a issue and PR is always welcomed.
@patpatbear Thanks for your feedback, which kvrocks version you're using? This PR: https://github.com/KvrocksLabs/kvrocks/pull/438 should help in this case, but I didn't have a try on my side.
Yes, too many tombstones would cause performance degrade when seeking the LSM Tree. For hash/set should only affect the command like hgetall, point lookup command like hget would be fine.
oh.. what your mean was that deleted tombstones would slowdown zadd?
cool, thanks @patpatbear. For this case, the single hot key indeed affects the performance in data race condition since we have the key lock when writing. I would investigate it...
I inspected this case, upper/lower bound help nothing since deletion tombstones may have the same prefix(same version). I'm not sure delete range whether can reduce the seek time or not...
@liangyuanpeng Thanks for your feedback, it makes a lot sense.
Thanks for @wanghenshui input, I'd like to have a try as well. Update: I tested the ping/ping_bulk which won't be affected by the data volume, and this PR improve the...