libvirt: increase master memory to 3GB #408
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci-robot
added
the
size/XS
Do we have time to dig into who's so hungry? Or are we just bumping this with the hope that we'll be able to circle back once things quiet down and tighten things up? Or is 3GB really reasonable for the sort of things the masters are doing? |
|
Haven't seen this |
@abhinavdahiya who is doing this? |
|
I am seeing this as well on my master node. |
|
@abhinavdahiya can we merge this if I promise to revert once we drop KCO? 👼 |
|
/approve |
openshift-ci-robot
added
the
approved
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, sjenning The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
cgwalters
added a commit
to cgwalters/installer
that referenced
this pull request
Dec 4, 2018
My main dev environment is a Lenovo P50 with 64GB of RAM - I got it specifically to run some large VMs (and/or many VMs) specifically with OpenShift in mind. Increasing RAM on my master to 8GB is a *very* noticeable speed improvement and I think reliabilty; before I saw the apiserver be `OOMKilled` sometimes, and `kswapd0` was constantly doing writeback. These variables aren't bubbled all the way up to the documented installer config, but one can now do e.g.: ``` $ env TF_VAR_tectonic_libvirt_memory=8192 TF_VAR_tectonic_libvirt_vcpu=4 ./bin/openshift-install create cluster --dir=osiris ``` Previously: - openshift#408 - openshift#163
cgwalters
added a commit
to cgwalters/installer
that referenced
this pull request
Dec 4, 2018
My main dev environment is a Lenovo P50 with 64GB of RAM - I got it specifically to run some large VMs (and/or many VMs) specifically with OpenShift in mind. First, default masters to 4096. And for me, increasing RAM on my master to 8GB is a *very* noticeable speed improvement and I think reliabilty; before I saw the apiserver be `OOMKilled` sometimes, and `kswapd0` was constantly doing writeback. These variables aren't bubbled all the way up to the documented installer config, but one can now do e.g.: ``` $ env TF_VAR_tectonic_libvirt_memory=8192 TF_VAR_tectonic_libvirt_vcpu=4 ./bin/openshift-install create cluster --dir=osiris ``` Previously: - openshift#408 - openshift#163
cgwalters
added a commit
to cgwalters/installer
that referenced
this pull request
Dec 5, 2018
My main dev environment is a Lenovo P50 with 64GB of RAM - I got it specifically to run some large VMs (and/or many VMs) specifically with OpenShift in mind. First, default masters to 4096 MiB since we are seeing a default install be overloaded. And for me, increasing RAM on my master to 8GB is a *very* noticeable speed improvement and I think reliabilty; before I saw the apiserver be `OOMKilled` sometimes, and `kswapd0` was constantly doing writeback. These variables aren't bubbled all the way up to the documented installer config, but one can now do e.g.: ``` $ env TF_VAR_libvirt_master_memory=8192 TF_VAR_libvirt_master_vcpu=4 ./bin/openshift-install create cluster --dir=osiris ``` Previously: - openshift#408 - openshift#163
cgwalters
added a commit
to cgwalters/installer
that referenced
this pull request
Dec 5, 2018
My main dev environment is a Lenovo P50 with 64GB of RAM - I got it specifically to run some large VMs (and/or many VMs) specifically with OpenShift in mind. First, default masters to 4096 MiB since we are seeing a default install be overloaded. And for me, increasing RAM on my master to 8GB is a *very* noticeable speed improvement and I think reliabilty; before I saw the apiserver be `OOMKilled` sometimes, and `kswapd0` was constantly doing writeback. These variables aren't bubbled all the way up to the documented installer config, but one can now do e.g.: ``` $ env TF_VAR_libvirt_master_memory=8192 TF_VAR_libvirt_master_vcpu=4 ./bin/openshift-install create cluster --dir=osiris ``` Previously: - openshift#408 - openshift#163
This was referenced Dec 5, 2018
Merged
add memory request to kube-apiserver and operator pods
openshift/cluster-kube-apiserver-operator#161
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After CVO merged, 2GB is no longer sufficient for master operations. The VM gridlocks with kswapd and becomes slow to respond or completely unresponsive.
I bumped my master to 4GB to get this working, but 3GB should be sufficient for now.
@aveshagarwal @derekwaynecarr @rphillips @abhinavdahiya