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

[wip]Feature/backend/index sharding part1 #747

Closed
wants to merge 21 commits into
base: develop
from

Conversation

Projects
None yet
1 participant
@gdchamal
Copy link
Member

gdchamal commented Jan 4, 2018

Currently an index is created per user, it's not a scalable design for elasticsearch and we must distribute differently data in index store.

We use a property User.shard_id to allocate many user per index and filter strictly per user_id when querying these indices.

@gdchamal gdchamal force-pushed the feature/backend/index-sharding-part1 branch 2 times, most recently from bd213dc to 1b30bc3 Jan 4, 2018

@gdchamal gdchamal force-pushed the feature/backend/index-sharding-part1 branch from 1b30bc3 to 25833ce Feb 8, 2018

@gdchamal

This comment has been minimized.

Copy link
Member

gdchamal commented Mar 20, 2018

Will proceed differently than this solution, too heavy

@gdchamal gdchamal closed this Mar 20, 2018

@iamdey iamdey deleted the feature/backend/index-sharding-part1 branch May 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment