[Bug] No Master Nodes Exist

[cristianCesanaIvolution]

Search before asking

• [X] I had searched in the issues and found no similar issues.

What happened

I deployed the last version of DolphinScheduler 3.2.1 through docker-compose procedure described here: https://dolphinscheduler.apache.org/en-us/docs/3.2.1/guide/start/docker#using-docker-compose-to-start-server

Running the monitor I can see that no master node exists

Tring to run a workflow or task I get the error "master does not exists" (as expected)

Looking at the logs contained in master container folder I can see this

Any idea of what is causing the master instance to not start correctly?

What you expected to happen

Worker instance is properly started and visible for dolphinscheduler-api container and tasks are executed correctly

How to reproduce

Deploy with docker-compose as described in: https://dolphinscheduler.apache.org/en-us/docs/3.2.1/guide/start/docker#using-docker-compose-to-start-server

Anything else

No response

Version

3.2.x

Are you willing to submit PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[fuchanghai]

hi @cristianCesanaIvolution It may be because the registered zk addresses of api-server and master-server are different, or the master is not registered on zk.

[bococ]

I also have this problem. After starting dolphinscheduler in version 3.2.0, the ports monitored by the master are 5678 and 5679. These two ports are also included in the configuration file. The configuration of 3.2.1 is the same, but the monitored port is only 5678.

[malinos88]

Bonjour, J'ai installé DolphinScheduler (docker/windows) et j'ai la même pb que vous (même msg d'erreur). Par contre je ne trouve pas de répertoire 'master-server'. L'avez-vous ajouté, se trouve t-il à la racine, ...? a+ fd

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

[zhixiangjoy]

meet the same problem, sos