Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [service down] service down and stop when use bash bin/start-all.sh a few seconds #16174

Closed
2 of 3 tasks
ArkURL opened this issue Jun 18, 2024 · 4 comments · Fixed by #16208
Closed
2 of 3 tasks
Assignees
Labels
bug Something isn't working discussion discussion

Comments

@ArkURL
Copy link

ArkURL commented Jun 18, 2024

Search before asking

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

What happened

I use cluster deploy to deploy dolphinscheduler service to 2 server.
server and service running env below:
os: centos7
db: postgresql-15.7
zookeeper: 3.7.2
python: python3.6
java: java-11

I deploy the service dolphinscheduler to 2 server and make them both be master-server and worker-server.
when use bash bin/start-all.sh, every service work well and run perfect, but a few second later, some master-server and worker-server went down, but some workflow still can run.

at the first time every server work well.
image

few seconds later, some server down but some workflow can still run.
image

how to solve it? here is two server's master-server log file.
dolphinscheduler-master.log
dolphinscheduler-master_2.log

What you expected to happen

service work well and not down.
dolphinscheduler-master_2.log
dolphinscheduler-master.log

How to reproduce

use cluster deploy and make them all master-server and worker-server.then start the service.

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

@ArkURL ArkURL added bug Something isn't working Waiting for reply Waiting for reply labels Jun 18, 2024
@SbloodyS SbloodyS added help wanted Extra attention is needed and removed Waiting for reply Waiting for reply labels Jun 18, 2024
@ruanwenjun
Copy link
Member

It's better to deprecated below six scripts, these scripts is not settled and I've rarely seen a project that offers a distributed deployment. @SbloodyS

image

@ruanwenjun ruanwenjun added the discussion discussion label Jun 18, 2024
@SbloodyS
Copy link
Member

SbloodyS commented Jun 19, 2024

It's better to deprecated below six scripts, these scripts is not settled and I've rarely seen a project that offers a distributed deployment. @SbloodyS

image

+1

I'll remove it in a few days.

@SbloodyS SbloodyS self-assigned this Jun 19, 2024
@SbloodyS SbloodyS removed the help wanted Extra attention is needed label Jun 19, 2024
@ruanwenjun
Copy link
Member

It's better to deprecated below six scripts, these scripts is not settled and I've rarely seen a project that offers a distributed deployment. @SbloodyS
image

+1

I'll remove it in a few days.

Thanks.

@ruanwenjun
Copy link
Member

@ArkURL Thanks for your report this problem, we plan to remove these kind of script, this means you should start the server in remote server after ssh login.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working discussion discussion
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants