Skip to content
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

CPU requests too high to run in minikube #132

Open
timothyb89 opened this issue Jul 26, 2017 · 0 comments
Open

CPU requests too high to run in minikube #132

timothyb89 opened this issue Jul 26, 2017 · 0 comments
Labels

Comments

@timothyb89
Copy link
Member

Our default resource limits no longer fit in default-ish Minikube:

[tim:~/projects/monasca-helm]↥ master+* ± kubectl describe node                               
Name:                   minikube
Role:
Labels:                 beta.kubernetes.io/arch=amd64
                        beta.kubernetes.io/os=linux
                        kubernetes.io/hostname=minikube
Annotations:            alpha.kubernetes.io/provided-node-ip=192.168.99.103
                        node.alpha.kubernetes.io/ttl=0
                        volumes.kubernetes.io/controller-managed-attach-detach=true
Taints:                 <none>
CreationTimestamp:      Wed, 26 Jul 2017 14:27:55 -0600
Phase:
Conditions:
  Type                  Status  LastHeartbeatTime                       LastTransitionTime                      Reason                          Message
  ----                  ------  -----------------                       ------------------                      ------                          -------
  OutOfDisk             False   Wed, 26 Jul 2017 15:54:38 -0600         Wed, 26 Jul 2017 14:27:55 -0600         KubeletHasSufficientDisk        kubelet has sufficient disk space available
  MemoryPressure        False   Wed, 26 Jul 2017 15:54:38 -0600         Wed, 26 Jul 2017 14:27:55 -0600         KubeletHasSufficientMemory      kubelet has sufficient memory available
  DiskPressure          False   Wed, 26 Jul 2017 15:54:38 -0600         Wed, 26 Jul 2017 14:27:55 -0600         KubeletHasNoDiskPressure        kubelet has no disk pressure
  Ready                 True    Wed, 26 Jul 2017 15:54:38 -0600         Wed, 26 Jul 2017 15:18:05 -0600         KubeletReady                    kubelet is posting ready status
Addresses:              192.168.99.103,minikube
Capacity:
 cpu:           2
 memory:        8175620Ki
 pods:          110
Allocatable:
 cpu:           2
 memory:        8073220Ki
 pods:          110
System Info:
 Machine ID:                    e0ef96460ab14eca9da83c47adfd687e
 System UUID:                   B348C521-45FB-4AE7-B4AD-C869ECB30DDD
 Boot ID:                       9ec42fce-8408-4472-b1e3-d467b1469d7c
 Kernel Version:                4.9.13
 OS Image:                      Buildroot 2017.02
 Operating System:              linux
 Architecture:                  amd64
 Container Runtime Version:     docker://1.12.6
 Kubelet Version:               v1.7.0
 Kube-Proxy Version:            v1.7.0
ExternalID:                     minikube
Non-terminated Pods:            (16 in total)
  Namespace                     Name                                            CPU Requests    CPU Limits      Memory Requests Memory Limits
  ---------                     ----                                            ------------    ----------      --------------- -------------
  kube-system                   kube-addon-manager-minikube                     5m (0%)         0 (0%)          50Mi (0%)       0 (0%)
  kube-system                   kube-dns-910330662-zh555                        260m (13%)      0 (0%)          110Mi (1%)      170Mi (2%)
  kube-system                   kubernetes-dashboard-6dqjh                      0 (0%)          0 (0%)          0 (0%)          0 (0%)
  kube-system                   tiller-deploy-3360264398-wk56v                  0 (0%)          0 (0%)          0 (0%)          0 (0%)
  monasca                       influx-init-job-v4fh8                           200m (10%)      500m (25%)      128Mi (1%)      256Mi (3%)
  monasca                       monasca-agent-2358686618-7z5cr                  200m (10%)      1 (50%)         512Mi (6%)      1Gi (12%)
  monasca                       monasca-agent-vlsq4                             200m (10%)      1 (50%)         512Mi (6%)      1Gi (12%)
  monasca                       monasca-aggregator-1374373255-58fsl             50m (2%)        250m (12%)      128Mi (1%)      256Mi (3%)
  monasca                       monasca-api-3476849549-p0j2v                    150m (7%)       2100m (105%)    384Mi (4%)      1280Mi (16%)
  monasca                       monasca-kafka-3025785492-dxvd7                  250m (12%)      2 (100%)        1Gi (12%)       2Gi (25%)
  monasca                       monasca-mysql-732161131-n51wb                   100m (5%)       500m (25%)      256Mi (3%)      1Gi (12%)
  monasca                       monasca-notification-2717193419-349n8           50m (2%)        500m (25%)      128Mi (1%)      256Mi (3%)
  monasca                       monasca-persister-2400452869-r94xf              50m (2%)        100m (5%)       128Mi (1%)      256Mi (3%)
  monasca                       monasca-storm-nimbus-3952265788-9bm2j           100m (5%)       500m (25%)      512Mi (6%)      2Gi (25%)
  monasca                       monasca-thresh-init-job-6j6gn                   256m (12%)      1 (50%)         256Mi (3%)      512Mi (6%)
  monasca                       monasca-zookeeper-2130261320-zpl36              100m (5%)       1 (50%)         256Mi (3%)      512Mi (6%)
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  CPU Requests  CPU Limits      Memory Requests Memory Limits
  ------------  ----------      --------------- -------------
  1971m (98%)   10450m (522%)   4384Mi (55%)    10666Mi (135%)
Events:
  FirstSeen     LastSeen        Count   From                    SubObjectPath   Type            Reason                  Message
  ---------     --------        -----   ----                    -------------   --------        ------                  -------
  45m           45m             1       kubelet, minikube                       Normal          Starting                Starting kubelet.
  45m           45m             1       kubelet, minikube                       Normal          NodeAllocatableEnforced Updated Node Allocatable limit across pods
  45m           45m             1       kubelet, minikube                       Normal          NodeHasSufficientDisk   Node minikube status is now: NodeHasSufficientDisk
  45m           45m             1       kubelet, minikube                       Normal          NodeHasSufficientMemory Node minikube status is now: NodeHasSufficientMemory
  45m           45m             1       kubelet, minikube                       Normal          NodeHasNoDiskPressure   Node minikube status is now: NodeHasNoDiskPressure
  45m           45m             1       kubelet, minikube                       Warning         Rebooted                Node minikube has been rebooted, boot id: eb9d309b-927d-4d1b-9d67-adb362abb3ce
  45m           45m             1       kube-proxy, minikube                    Normal          Starting                Starting kube-proxy.
  36m           36m             1       kubelet, minikube                       Normal          NodeAllocatableEnforced Updated Node Allocatable limit across pods
  36m           36m             1       kubelet, minikube                       Normal          Starting                Starting kubelet.
  36m           36m             1       kubelet, minikube                       Normal          NodeHasSufficientDisk   Node minikube status is now: NodeHasSufficientDisk
  36m           36m             1       kubelet, minikube                       Normal          NodeHasSufficientMemory Node minikube status is now: NodeHasSufficientMemory
  36m           36m             1       kubelet, minikube                       Normal          NodeHasNoDiskPressure   Node minikube status is now: NodeHasNoDiskPressure
  36m           36m             1       kubelet, minikube                       Warning         Rebooted                Node minikube has been rebooted, boot id: 9ec42fce-8408-4472-b1e3-d467b1469d7c
  36m           36m             1       kubelet, minikube                       Normal          NodeNotReady            Node minikube status is now: NodeNotReady
  36m           36m             1       kube-proxy, minikube                    Normal          Starting                Starting kube-proxy.
  36m           36m             1       kubelet, minikube                       Normal          NodeReady               Node minikube status is now: NodeReady

This configuration leaves about 7 pods unable to start due to CPU requests exceeding the 2 cores available by default to Minikube. Obviously Monasca can run in less than that, so we can probably lower requests by quite a bit. I think the init jobs and agents are good candidates to have their requests lowered.

@timothyb89 timothyb89 added the bug label Jul 26, 2017
@timothyb89 timothyb89 changed the title Adjust resource requests CPU requests too high to run in minikube Jul 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant