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

Create additional Couchbase backends during install #450

Open
yurem opened this Issue Jul 4, 2018 · 3 comments

Comments

Projects
None yet
4 participants
@yurem
Contributor

yurem commented Jul 4, 2018

We need to create 5 buckets per this config to split data between buckets and allow to specify their type for optional performance.

Here is full list of buckets: gluu (default), gluu_user (for ou=people/ou=group), gluu_session (ou=sessions), gluu_statistic(ou=metric), gluu_site(o=site).

gluu_session should has type Memcached

Based on this we need to create proper index in each bucket.

@nynymike @mbaser @afroDC Do you have any suggestions about this?

@yurem yurem added this to the 4.0 milestone Jul 4, 2018

@yurem yurem changed the title from Create additional Cocubase backends during install to Create additional Couchbase backends during install Jul 4, 2018

@yuriyz

This comment has been minimized.

Contributor

yuriyz commented Jul 4, 2018

@yurem according to GluuFederation/oxCore#83 we need add Couchbase cache provider. I guess we need ou=cache bucket for it.

@afroDC

This comment has been minimized.

Contributor

afroDC commented Jul 6, 2018

specify their type for optional performance.

Can you elaborate on how they can specify their type?

gluu (default)

I'm assuming this bucket will take everything not included in sessions, group/people, metric and site, right?

@mbaser

This comment has been minimized.

Collaborator

mbaser commented Jul 6, 2018

I implemented this by commit c34f217
However, current version of gluu is not working when additional buckets created, for this reason I commented them. Additionally:

  1. we also need to identify which indexes should be created on each bucket,
  2. determine how application ram will be distributed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment