Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addition of a pre-populated replica #412

Open
a0d00kc opened this issue Apr 12, 2023 · 0 comments
Open

Addition of a pre-populated replica #412

a0d00kc opened this issue Apr 12, 2023 · 0 comments

Comments

@a0d00kc
Copy link

a0d00kc commented Apr 12, 2023

Hi Folks,

First of sorry if this not the right channel to raise queries. We are exploring memcached + mcrouter as unified caching solution for our org. One place where we are stuck (or unable to understand) is, say we are adding a new memcached pod as replica to the replica pool, from what I understand the replica will get populated gradually through the writes which will be result of cache misses on this newly added replica. If this is the case, an addition of replica will cause sudden increase in traffic on our cold store, there by we are exploring options/mechanism, if available out of the box with mcrouter, through which we can pre-populate key values on the replica and set it up for active reads. From a consistency angle, we can live with some level of inconsistency.

Thanks in advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant