Question: Writing to multiple masters

[rohitjoshi]

Can Onecache be configured to write to two or more masters? May be using pipepine to replicate on 2nd master.

[anysql]

Why not do it based on the current redis replication feature?

[rohitjoshi]

@anysql my understanding is that current Redis replication doesn't support master/master replication.
My requirements are

1. Traffic will be routed to the east and west coast equally (50-50%)
2. Every request will update timestamp on the token which will be stored in the redis cluster which means write is required on both the clusters (east and west) if user's requests are routed to east and west coast.

There are three ways to solve this.

1. master-master replication
2. client/proxy writes to both the cluster (possibly asynchronously to the 2nd cluster)
3. Use hashing mechanism and route request to always the east or west coast based on the hash. This might add higher latency if write happens across the region.

Let me know your suggestion.

[anysql]

1, How heavy is the write traffic?
2, We have another project named "OneValue", which support master<->master replication and a timestamp based confilict solution. It's persistent KV storage with Redis protocol compatible, and has mutliple work threads for better single instance performance.

Thanks.

[rohitjoshi]

1. Expected peak TPS is ~10k
2. I have looked at it. Redis is approved product for cache usage so we may not be able to use onevalue.