Updating CPU limitation in abctl

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

How to update CPU limitation in abctl?


Question

Hello anyone knows to update cpu limitation in abctl ?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["update", "cpu-limitation", "abctl", "platform"]
2

Hello Alan, this means your machine or docker has access to less cpu than required by the application. You can check more about the recommended resources or how to run using --low-resource mode here: https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart#suggested-resources

3

Hello <@U01MMSDJGC9> my machine has 16gb of RAM and 6cpus (is a virtual machine on GCP) :confused:

4

How many connections do you have? Are they running in parallel?

5

What is the output of docker info?

6

this is the output <@U01MMSDJGC9>

 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.5
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 1
  Running: 1
  Paused: 0
  Stopped: 0
 Images: 23
 Server Version: 25.0.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.10.0-32-cloud-amd64
 Operating System: Debian GNU/Linux 11 (bullseye)
 OSType: linux
 Architecture: x86_64
 CPUs: 6
 Total Memory: 15.63GiB
 Name: airbyte-vm
 ID: 21bb7e08-fef8-4b9a-ad90-ff686e1fd5f8
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false```
7

<@U01MMSDJGC9> Is there a way to modify the CPU and memory limits set in the pod manifests?

8

I have find the fix (or issue?), if --low-resource is used, the limitations are removed and all works