confluentinc / confluentinc/examples

Confluent Replicator Demo Issue: Reporting error "Waiting up to 180 seconds for Connect to start"

Open
#1,019 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
2.1k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

Hello,

Following the steps to run the demo on Confluent replicator. It is stuck while launching the Connect cluster with the error shown below in the output. Appreciate any input.

**Link**: https://docs.confluent.io/platform/current/multi-dc-deployments/replicator/replicator-docker-tutorial.html#environment

**Output:**
Creating broker-dc1 ... done
Creating schema-registry-dc1 ... done
Creating schema-registry-dc2 ... done
Creating datagen-dc1-topic1 ... done
Creating datagen-dc1-topic2 ... done
Creating connect-dc2 ... done
Creating datagen-dc2-topic1 ... done
Creating connect-dc1 ... done
Creating control-center ... done
Waiting up to 180 seconds for Connect to start
.......................
Waiting up to 180 seconds for Connect to start
....................................ERROR: Failed after 180 seconds. Please troubleshoot and run again.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the tutorial's Environment section and the Docker startup output, then investigate why connect-dc1 and connect-dc2 do not become ready within 180 seconds. Done means reproducing the failure, identifying the responsible configuration or startup condition, and documenting a verified troubleshooting path.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.