/juju

Simplify mongo opLogSize calculation #7392

Merged
merged 1 commit into from May 25, 2017

Conversation

Reviewers

@wallyworld wallyworld

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@wupeka @jujubot @wallyworld
@wupeka
Member

wupeka commented May 25, 2017 •
Edited 1 time

Description of change

The previous method was based on available disk space:

  • 512MB if below 10G
  • linearly from 512MB to 1G for 10G to 20G
  • 1G for above 20G
    Since each change in opLogSize requires restarting mongo restarting jujud while available disk space was varying between 10G and 20G caused mongo restart, which could cause problems in HA environments.
    The new method is simply 512MB if available disk space below 15G, 1G if above - this should limit mongo restarts to minimum.

QA steps

Bootstrap controller with 50G free space available, fill the disk to 18G available, restart jujud, verify that mongo wasn't restarted, fill the disk to 13G available, restart jujud, verify that mongo was restarted, fill the disk to 5G available, verify that mongo wasn't restarted.

Documentation changes

None

Bug reference

https://bugs.launchpad.net/juju/+bug/1677592
@wupeka
Member

wupeka commented May 25, 2017

$$merge$$
@jujubot
Contributor

jujubot commented May 25, 2017

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju

@jujubot jujubot merged commit 9761475 into juju:develop May 25, 2017
1 check passed

1 check passed

github-check-merge-juju Built PR, ran unit tests, and tested LXD deploy. Use !!.*!! to request another build. IE, !!build!!, !!retry!!
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment