search

datahub-project / datahub

The Metadata Platform for your Data Stack
https://datahubproject.io
Apache License 2.0
9.69k stars 2.86k forks source link

Quickstart DataHub not found - Container dependency datahub-schema-registry failed #10734

Open dsalgueiror opened 3 months ago

dsalgueiror commented 3 months ago

Describe the bug Quickstart DataHub not found - Container dependency datahub-schema-registry failed

broker-1               | [2024-06-18 05:29:52,956] INFO [GroupCoordinator 1]: Member sr-1-a6e11473-80b3-4bc7-8d38-f78ed144fd27 in group schema-registry has failed, removing it from the group (kafka.coordinator.group.GroupCoordinator)
broker-1               | [2024-06-18 05:29:52,962] INFO [GroupCoordinator 1]: Preparing to rebalance group schema-registry in state PreparingRebalance with old generation 1 (__consumer_offsets-29) (reason: removing member sr-1-a6e11473-80b3-4bc7-8d38-f78ed144fd27 on heartbeat expiratio
n) (kafka.coordinator.group.GroupCoordinator)
broker-1               | [2024-06-18 05:29:52,966] INFO [GroupCoordinator 1]: Group schema-registry with generation 2 is now empty (__consumer_offsets-29) (kafka.coordinator.group.GroupCoordinator)
broker-1               | [2024-06-18 05:29:56,998] INFO [GroupCoordinator 1]: Dynamic member with unknown member id joins group schema-registry in Empty state. Created a new member id sr-1-b6f2c3f4-0b45-4aac-9c1d-c6553c0dab8c and request the member to rejoin with this id. (kafka.coordi
nator.group.GroupCoordinator)
broker-1               | [2024-06-18 05:29:57,008] INFO [GroupCoordinator 1]: Preparing to rebalance group schema-registry in state PreparingRebalance with old generation 2 (__consumer_offsets-29) (reason: Adding new member sr-1-b6f2c3f4-0b45-4aac-9c1d-c6553c0dab8c with group instance
id None; client reason: rebalance failed due to MemberIdRequiredException) (kafka.coordinator.group.GroupCoordinator)
broker-1               | [2024-06-18 05:29:57,016] INFO [GroupCoordinator 1]: Stabilized group schema-registry generation 3 (__consumer_offsets-29) with 1 members (kafka.coordinator.group.GroupCoordinator)
broker-1               | [2024-06-18 05:29:57,044] INFO [GroupCoordinator 1]: Assignment received from leader sr-1-b6f2c3f4-0b45-4aac-9c1d-c6553c0dab8c for group schema-registry for generation 3. The group has 1 members, 0 of which are static. (kafka.coordinator.group.GroupCoordinator)
broker-1               | [2024-06-18 05:34:47,423] INFO [Controller id=1] Processing automatic preferred replica leader election (kafka.controller.KafkaController)
broker-1               | [2024-06-18 05:34:47,423] TRACE [Controller id=1] Checking need to trigger auto leader balancing (kafka.controller.KafkaController)
broker-1               | [2024-06-18 05:34:47,425] DEBUG [Controller id=1] Topics not in preferred replica for broker 1 HashMap() (kafka.controller.KafkaController)
broker-1               | [2024-06-18 05:34:47,425] TRACE [Controller id=1] Leader imbalance ratio for broker 1 is 0.0 (kafka.controller.KafkaController)

To Reproduce Steps to reproduce the behavior: 1-datahub docker quickstart 2-Edit docker-compose.yml timeouts to more than double in case it was a problem that the boot was being interrupted but the problem persists

Expected behavior That the system quickstart starts with all the containers

Screenshots

[+] Running 7/7
 ✔ Container datahub-mysql-1                Healthy                                                                                                                                                                                                                                    0.5s
 ✔ Container datahub-elasticsearch-1        Healthy                                                                                                                                                                                                                                      0.5s
 ✔ Container datahub-zookeeper-1            Healthy                                                                                                                                                                                                                                      0.5s
 ✔ Container datahub-elasticsearch-setup-1  Started                                                                                                                                                                                                                                      1.1s
 ✔ Container datahub-mysql-setup-1          Started                                                                                                                                                                                                                                      1.0s
 ✔ Container datahub-broker-1               Healthy                                                                                                                                                                                                                                      1.5s
 ✘ Container datahub-schema-registry-1      Error                                                                                                                                                                                                                                        1.5s
dependency failed to start: container datahub-schema-registry-1 is unhealthy

Unable to run quickstart - the following issues were detected:
- elasticsearch container is not present
- schema-registry container is not present
- datahub-gms container is not present
- elasticsearch-setup container is not present
- broker container is not present
- datahub-frontend-react container is not present
- zookeeper container is not present
- kafka-setup container is not present

If you think something went wrong, please file an issue at https://github.com/datahub-project/datahub/issues
or send a message in our Slack https://slack.datahubproject.io/
Be sure to attach the logs from /tmp/tmpa7oee_e5.log

Desktop (please complete the following information):

Additional context Attach logs /tmp/tmpa7oee_e5.log tmpa7oee_e5.log

dsalgueiror commented 3 months ago

The problem is ports in use and their modification/adaptation such as 8080 or 8081 is not allowed since when changing them in docker-compose.yml to other free ones the solution does not start correctly.