> On 16 May 2019, at 16:21, aravind gosukonda <arabha...@gmail.com> wrote: > >> If the container is removed, you need to do a cleanallruv on shutdown, and >> purge the >> volume so the replica ID can be reused. So you likely only have autoscaling >> to *grow* >> covered, but not to shrink. > Yes, that's true. I hadn't thought of autoscaling for shrink. Probably a part > of next phase of our deployment. :) >
Shrinking is the much harder part. This is why I'd recommend you have a static number of writable servers/containers, and then scale the read-onlies, because they are a bit easier to manage in this regard (no need to cleanruv etc). Glad to have helped you with this thought process. > Thanks, > Aravind > _______________________________________________ > 389-users mailing list -- 389-users@lists.fedoraproject.org > To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
