[Improve][Seatunnel-Cluster] Run the server through daemon

[liugddx]

Purpose of this pull request

Check list

• Code changed are covered with tests, or it does not need tests for reason:
• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update change log that in connector document. For more details you can refer to connector-v2
  2. Update plugin-mapping.properties and add new connector information in it
  3. Update the pom file of seatunnel-dist
• Update the release-note.

[liugddx]

[TyrantLucifer]

Please fix CI error

[TyrantLucifer]

seatunnel-cluster.sh dose not only has the one function to start cluster node, it also has the function of showing help message like the following shown:

So if using this solution user will not see the help message realtime.

[TyrantLucifer]

seatunnel-cluster.sh dose not only has the one function to start cluster node, it also has the function of showing help message like the following shown:

So if using this solution user will not see the help message realtime.

cc @Hisoka-X @EricJoy2048

[Hisoka-X]

yes, you should put -d to start cluster with daemon mode.

seatunnel-cluster.sh dose not only has the one function to start cluster node, it also has the function of showing help message like the following shown:

So if using this solution user will not see the help message realtime.

cc @Hisoka-X @EricJoy2048

[liugddx]

yes, you should put -d to start cluster with daemon mode.

seatunnel-cluster.sh dose not only has the one function to start cluster node, it also has the function of showing help message like the following shown:

So if using this solution user will not see the help message realtime.

cc @Hisoka-X @EricJoy2048

Agree with you

[liugddx]

[TyrantLucifer]

If user input seatunnel.sh -h -d or seatunnel.sh -xxx -d, the output log of option -xxx will be rewrited in files too.

[Hisoka-X]

I use your changed in local, report this error when SeaTunnel don't have seatunnel-server.out.

[liugddx]

If user input seatunnel-cluster.sh -h -d or seatunnel-cluster.sh -xxx -d, the output log of option -xxx will be rewrited in files too.

We can not use -d if it is an interactive argument. So seatunnel-cluster.sh -h -d is not allowed, but the internal parameters of the program can be parsed, like seatunnel-cluster.sh -cn test_seatunnel -d, Have any good Suggestions?

I use your changed in local, report this error when SeaTunnel don't have seatunnel-server.out.

I'm in deployment.md illustrates this .

mkdir -p $SEATUNNEL_HOME/logs
touch $SEATUNNEL_HOME/logs/seatunnel-server.out
./bin/seatunnel-cluster.sh -d

[Hisoka-X]

LGTM

[Hisoka-X]

LGTM