bin/start.sh only allows one process

[dbrimley]

Try starting two hazelcast instances using the ./bin/start.sh script.

Because there is only very basic PID management it fails and asks the user to create another copy of the bin directory. This is poor user experience.

I've tested other distributions from Redis and Kafka. They provide more advanced PID management that allows running multiple processes.

Allow start.sh to run more processes without the need to copy the bin directory. In hand with this the /bin/stop.sh script should take a PID.

[pveentjer]

Will this not cause issues with e.g. logging? So having 2 or more Hazelcast processes sharing the logging directory. If the log filesnames are unique, it is ok, but if they are not then there could be a serious problem.

[dbrimley]

Hazelcast Jet allows multiple processes to be started, it doesn't store any pid state on the file system. The stop script just greps for Jet processes and kills them all in one go.

[alparslanavci]

Fixed by #15934