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. I have installed locally via command abctl local install

It’s possible that everything is configured correctly but the job is genuinely stuck; however, the knowledge sources don’t provide a specific, documented cause for Couchbase→Postgres syncs hanging, so the guidance below is based only on general patterns of “stuck” syncs and abctl deployments. A few concrete checks and actions you can take: 1. Confirm your abctl deployment is healthy Since you installed with

abctl local install

, first verify the local cluster and Airbyte app are actually up and running:

abctl local status

You should see the Airbyte Helm chart in

Status: deployed

and a URL like

http://localhost:8000

. [abctl local] If things look off, you can restart the Kubernetes workloads:

abctl local deployments --restart

And, if needed, fully uninstall and reinstall:

abctl local uninstall
   abctl local install

Note that

abctl local install

can take a long time (up to ~30 minutes or more depending on network and resources). [abctl local; abctl issue] 2. Check for resource constraints Several forum threads describe syncs “getting stuck” or “hanging” with no clear error, often related to resource pressure (CPU/memory) even when it doesn’t look maxed out at first glance. [Syncs stuck; Postgres stuck; Records read stuck] On your local machine, while the sync is “queued” or “running”: ◦ Check system resources (CPU, RAM, disk I/O). ◦ Check Kubernetes pod status via

kubectl

(if you have access through abctl’s kubeconfig) to see if any connector pods are CrashLooping or Pending. The knowledge sources don’t provide exact resource recommendations for Couchbase→Postgres, but one abctl issue suggests that 2 CPUs can be “very tight” and recommends at least 4 CPUs and 8 GB RAM for smoother operation. [abctl issue] 3. Verify Couchbase source configuration Ensure the Couchbase source is correctly configured and reachable: ◦ Valid connection string (e.g.

couchbase://localhost

or Capella URL). ◦ Correct username/password and bucket name. ◦ Couchbase server ≥ 7.0 and the bucket actually contains the data you expect. [Couchbase source] If the source can’t list collections or read data, the sync may appear stuck early in the pipeline. 4. Look at the sync logs The forum posts about “stuck” syncs all rely on examining the job logs to understand where it’s hanging (source read vs. destination write vs. orchestration). [Mixpanel stuck; Postgres stuck; Records read stuck; Syncs getting stuck] In the Airbyte UI: ◦ Open the connection → “Jobs” → click the running (or last) sync → “Logs”. ◦ Check whether: ▪︎ It’s stuck before reading any records from Couchbase. ▪︎ It reads records but never starts writing to Postgres. ▪︎ It finishes reading but hangs on finalization. The knowledge sources don’t include a specific log pattern for Couchbase→Postgres hangs, so if the logs don’t show progress for a long time and no errors, that’s a strong sign of a stuck job. 5. Cancel and retry the sync Several users report that cancelling and re-running the sync sometimes clears transient issues. [Mixpanel stuck; Postgres stuck] ◦ Cancel the current job in the UI. ◦ Start a new sync. ◦ If it gets stuck again at the same stage, capture and save the logs. 6. If it keeps happening The knowledge sources do not document a known bug specific to Couchbase→Postgres with 1 GB of data, so if: ◦

abctl local status

is healthy, ◦ resources look reasonable, ◦ Couchbase and Postgres configs are correct, ◦ and the job still repeatedly hangs, then the next step is to share the job logs with Airbyte support or on the community forum for deeper analysis, as suggested in similar “stuck sync” threads. [Mixpanel stuck; Restart from tmp] ------------------------- If you can paste the relevant part of the sync logs (or describe where in the log it stops progressing), I can help you interpret them based on the patterns shown in the referenced issues and docs. 👍 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 221643 destination INFO DefaultDispatcher-worker-1 i.a.i.d.p.c.PostgresAirbyteClient(execute):444 BEGIN TRANSACTION; DROP TABLE IF EXISTS "Couchbase_countryinfo"."Couchbasntryinfocountryi_default293bdb99e3a0980c64b6310f2c582bfc"; CREATE TABLE IF NOT EXISTS "Couchbase_countryinfo"."Couchbasntryinfocountryi_default293bdb99e3a0980c64b6310f2c582bfc" ( "_airbyte_raw_id" varchar NOT NULL, "_airbyte_extracted_at" timestamp with time zone NOT NULL, "_airbyte_meta" jsonb NOT NULL, "_airbyte_generation_id" bigint NOT NULL, "_id" varchar, "_default" jsonb, "_ab_cdc_updated_at" bigint ); COMMIT; 2026-02-20 221643 destination INFO DefaultDispatcher-worker-1 i.a.i.d.p.c.PostgresAirbyteClient(execute):444 CREATE INDEX IF NOT EXISTS "idx_pk_Couchbasntryinfocountryi_default293bdb99e3a0980c64b6310f2c582bfc" ON "Couchbase_countryinfo"."Couchbasntryinfocountryi_default293bdb99e3a0980c64b6310f2c582bfc" ("_id"); CREATE INDEX IF NOT EXISTS "idx_cursor_Couchbasntryinfocountryi_default293bdb99e3a0980c64b6310f2c582bfc" ON "Couchbase_countryinfo"."Couchbasntryinfocountryi_default293bdb99e3a0980c64b6310f2c582bfc" ("_ab_cdc_updated_at"); CREATE INDEX IF NOT EXISTS "idx_extracted_at_Couchbasntryinfocountryi_default293bdb99e3a0980c64b6310f2c582bfc" ON "Couchbase_countryinfo"."Couchbasntryinfocountryi_default293bdb99e3a0980c64b6310f2c582bfc" ("_airbyte_extracted_at"); 2026-02-20 221643 destination INFO DefaultDispatcher-worker-1 i.a.c.l.d.DestinationLifecycle$initializeIndividualStreams$1$result$1$1(invokeSuspend):69 Stream loader for stream Couchbase-countryinfo:countryinfo._default._default started 2026-02-20 221643 destination INFO main i.a.c.l.d.p.PipelineRunner(run):40 Destination Pipeline Starting... 2026-02-20 221643 destination INFO main i.a.c.l.d.p.PipelineRunner(run):42 Starting state reconciler... 2026-02-20 221643 destination INFO main i.a.c.l.d.p.PipelineRunner(run):45 Starting 1 pipelines...