Kubernetes job resources - limits

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: ----
  • Memory / Disk: –
  • Deployment: Kubernetes deployment
  • Airbyte Version: 0.40.29?
  • Source name/version: —
  • Destination name/version: airbyte/destination-mssql:0.1.22
  • Step: Connection creation
  • Description:


I’ve encountered issue with setting up the limits for jobs. Iam using the mssql-destination connector.
I went through Configuring Connector Resources | Airbyte Documentation
and airbyte/config.yaml at master · airbytehq/airbyte (github.com)
and ran this query afterwards

update actor_definition set resource_requirements = '{"default": {"cpu_limit": "0.5", "cpu_request": "0.5", "memory_limit": "500Mi", "memory_request": "500Mi"},"jobSpecific": [{"jobType": "sync", "resourceRequirements": {"cpu_limit": "0.5", "cpu_request": "0.5", "memory_limit": "500Mi", "memory_request": "500Mi"}}, {"jobType": "check_connection", "resourceRequirements": {"cpu_limit": "0.5", "cpu_request": "0.5", "memory_limit": "500Mi", "memory_request": "500Mi"}},{"jobType": "get_spec", "resourceRequirements": {"cpu_limit": "0.5", "cpu_request": "0.5", "memory_limit": "500Mi", "memory_request": "500Mi"}},{"jobType": "discover_schema", "resourceRequirements": {"cpu_limit": "0.5", "cpu_request": "0.5", "memory_limit": "500Mi", "memory_request": "500Mi"}},{"jobType": "reset_connection", "resourceRequirements": {"cpu_limit": "0.5", "cpu_request": "0.5", "memory_limit": "500Mi", "memory_request": "500Mi"}},{"jobType": "connection_updater", "resourceRequirements": {"cpu_limit": "0.5", "cpu_request": "0.5", "memory_limit": "500Mi", "memory_request": "500Mi"}},{"jobType": "replicate", "resourceRequirements": {"cpu_limit": "0.5", "cpu_request": "0.5", "memory_limit": "500Mi", "memory_request": "500Mi"}}]}' where docker_repository like '%mssql%';

The value is correctly set in the DB and is picked up by the server, at least for schema validation.

However, the actual job definition in kubernetes is untouched. This is problematic for me, as empty resource limits are supplied by our clusters with some hilariously small values, resulting in the job failure.
Can anybody advise on how the limits can be set on check_connection jobs?

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

I am encountering a similar problem, where the resourceRequirements for the jobType ‘discover_schema’ are ignored when the discovery-pods are created in Kubernetes.

The resourceRequirements for jobType ‘sync’ seems to be working fine though.

I have also discovered that the JOB_MAIN_CONTAINER_MEMORY_LIMIT/REQUEST env var values are actually used for resource limits for discovery-pods as well as sync jobs when they are set.

The difference being that this default value for sync jobs is overruled by the actor_definition resource-requirements for sync jobs, while this default value for discovery jobs does not seem to be influenced by the actor_definition resource-requirements for discover_schema jobs.

I am currently using Airbyte 40.13.

Any update on this?
Is this intended behaviour?
Has this behaviour changed in a future versions?

1 Like