You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue would be that twemproxy isn't aware of the signature of the commands, so it doesn't know if a command has multiple keys, needs to be fragmented to multiple servers, is synchronous and able to be forwarded (i.e. not pubsub), etc. https://oss.redis.com/redisbloom/Bloom_Commands/ and related pages would be useful as a reference for anyone implementing that, this seems to be single-key commands
This kind of requirement increases the number of string matching for not needing this module, which may have a little impact on performance, whether it needs to be merged into the main branch or as an independent branch.
For keys, the commands in the https://oss.redis.com/redisbloom/Bloom_Commands/ document are all single-key, so the proxy can focus on forwarding and does not need to be split into multiple shards.
twemproxy has been used by us.
Now we want to use the bloom filter modules.
What should I do?
The text was updated successfully, but these errors were encountered: