Hi, I am exploring airbyte where need to replicate data from couchbase server to postgresql, I have created source and destination and start the sync but it stuck in queue from last 2 hours where couchbase bucket data is 1GB only

It sounds like you’ve set up Couchbase → Postgres correctly, but the job itself is never leaving the “queued” state. From the knowledge we have, there isn’t a Couchbase-specific bug documented for this; instead, similar “stuck / hanging / queued” syncs are usually related to: • Not enough worker capacity / resources, so the job never actually starts (common on Docker/Kubernetes deployments). [Syncs stuck; Syncs getting stuck] • Airbyte worker pods/containers being stuck in

Pending

or otherwise not scheduled. [Syncs stuck] • General resource constraints (CPU/RAM) or environment limits that prevent the worker from being created. [Airbyte resources] Given that: 1. Check whether the worker actually started ◦ In the Airbyte UI, open the connection, go to the last job, and download/view the logs. ◦ If there are no source/destination logs at all, the job likely never left the queue (no worker was started). 2. Inspect your deployment resources ◦ If you’re on Kubernetes: check if the

airbyte-worker

pod for this job is in

Pending

or

CrashLoopBackOff

. [Syncs stuck] ◦ If you’re on Docker: run

docker ps

/

docker stats

and see whether a worker container is created and whether CPU/RAM are close to limits. [Airbyte resources] 3. Try a smaller test sync ◦ Create a new connection from the same Couchbase bucket but limit it to a single small collection/stream and run a sync. ◦ If the small sync starts and finishes, the issue is more likely capacity/limits when handling the full 1 GB dataset. 4. Check Couchbase connector basics ◦ Ensure the Couchbase source is configured against a healthy 7.0+ server/Capella cluster and that the bucket/collections are accessible. [Couchbase source] ◦ The connector will try to read all collections in the bucket as streams; if there are many collections, that can increase load. [Couchbase source] Because the provided sources don’t include a direct fix for “job stuck in queue for Couchbase → Postgres”, I can’t point to a specific bug or patch. The next concrete steps would be: • Share/download the job logs for this connection and confirm whether a worker ever starts. • Check your environment (Docker/K8s) for pending/stuck worker containers/pods and resource limits. • If logs show nothing and workers are pending, you’ll likely need to increase available resources or adjust your scheduler/cluster so Airbyte workers can be scheduled. If you can paste the job logs (or confirm whether there are any source/destination logs at all), I can help you interpret them based only on what’s documented. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

2026-02-20 221537 platform INFO APPLY Stage: BUILD — (workloadId=88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check) 2026-02-20 221537 platform INFO APPLY Stage: CLAIM — (workloadId=88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check) 2026-02-20 221537 platform INFO Claimed: true for workload 88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check via API in dataplane 2ec0dbdd-4650-4283-83eb-dc9ee24aef7e (335b2065-652f-4897-ba89-077666100ebb) 2026-02-20 221537 platform INFO APPLY Stage: LOAD_SHED — (workloadId=88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check) 2026-02-20 221537 platform INFO APPLY Stage: CHECK_STATUS — (workloadId=88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check) 2026-02-20 221537 platform INFO No pod found running for workload 88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check 2026-02-20 221537 platform INFO APPLY Stage: MUTEX — (workloadId=88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check) 2026-02-20 221537 platform INFO No mutex key specified for workload: 88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check. Continuing... 2026-02-20 221537 platform INFO APPLY Stage: ARCHITECTURE — (workloadId=88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check) 2026-02-20 221537 platform INFO APPLY Stage: LAUNCH — (workloadId=88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check) 2026-02-20 221537 platform INFO [initContainer] image: airbyte/workload-init-container:2.0.1 resources: ResourceRequirements(claims=[], limits={}, requests={}, additionalProperties={}) 2026-02-20 221546 platform INFO Attempting to update workload: 88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check to LAUNCHED. 2026-02-20 221546 platform INFO Pipeline completed for workload: 88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check. 2026-02-20 221550 platform INFO 2026-02-20 221550 platform INFO Transitioning workload to running state 2026-02-20 221550 platform INFO ----- START CHECK ----- 2026-02-20 221550 platform INFO 2026-02-20 221550 platform INFO Workload successfully transitioned to running state 2026-02-20 221551 platform INFO Connector exited, processing output 2026-02-20 221551 platform INFO Output file jobOutput.json found 2026-02-20 221551 platform INFO Connector exited with exit code 0 2026-02-20 221551 source INFO Reading messages from protocol version 0.2.0 2026-02-20 221551 source INFO Successfully connected to Couchbase cluster and bucket 2026-02-20 221551 source INFO Check succeeded 2026-02-20 221551 platform INFO Checking for optional control message... 2026-02-20 221551 platform INFO Writing output of 88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check to the doc store 2026-02-20 221551 platform INFO Marking workload 88b373ec-c4f3-4a59-a307-2e081c9eaf21_5_0_check as successful 2026-02-20 221551 platform INFO 2026-02-20 221551 platform INFO Deliberately exiting process with code 0. 2026-02-20 221551 platform INFO ----- END CHECK ----- 2026-02-20 221551 platform INFO 2026-02-20 221552 platform INFO APPLY Stage: BUILD — (workloadId=bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check) 2026-02-20 221552 platform INFO APPLY Stage: CLAIM — (workloadId=bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check) 2026-02-20 221552 platform INFO Claimed: true for workload bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check via API in dataplane 2ec0dbdd-4650-4283-83eb-dc9ee24aef7e (335b2065-652f-4897-ba89-077666100ebb) 2026-02-20 221552 platform INFO APPLY Stage: LOAD_SHED — (workloadId=bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check) 2026-02-20 221552 platform INFO APPLY Stage: CHECK_STATUS — (workloadId=bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check) 2026-02-20 221552 platform INFO No pod found running for workload bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check 2026-02-20 221552 platform INFO APPLY Stage: MUTEX — (workloadId=bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check) 2026-02-20 221552 platform INFO No mutex key specified for workload: bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check. Continuing... 2026-02-20 221552 platform INFO APPLY Stage: ARCHITECTURE — (workloadId=bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check) 2026-02-20 221552 platform INFO APPLY Stage: LAUNCH — (workloadId=bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check) 2026-02-20 221552 platform INFO [initContainer] image: airbyte/workload-init-container:2.0.1 resources: ResourceRequirements(claims=[], limits={}, requests={}, additionalProperties={}) 2026-02-20 221559 platform INFO Attempting to update workload: bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check to LAUNCHED. 2026-02-20 221559 platform INFO Pipeline completed for workload: bd904277-c5f7-4908-b607-ad87cad8513d_5_0_check. 2026-02-20 221602 platform INFO 2026-02-20 221602 platform INFO Transitioning workload to running state 2026-02-20 221602 platform INFO ----- START CHECK ----- 2026-02-20 221602 platform INFO 2026-02-20 221602 platform INFO Workload successfully transitioned to running state 2026-02-20 221603 platform INFO Connector exited, processing output