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.

Sign up for GitHub

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

Jump to bottom

Don't change geo-pin algo b/c of bad VDC #3

Open
marrotte opened this issue Feb 24, 2017 · 0 comments
Open

Don't change geo-pin algo b/c of bad VDC #3

marrotte opened this issue Feb 24, 2017 · 0 comments

Comments

@marrotte
Copy link

Currently, when an unhealthy VDC is detected while geo-pinning, the client changes the operand in the mod operation to reflect the number of healthy or good VDC. This new healthy VDC count is used to compute the geo-pinned VDC for every request versus just handling the bad VDC-pinned objects. Computing a new VDC just for the bad VDC requests would guarantee less data placed in the "wrong" VDC.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@marrotte