1. Reason
In a distributed test environment, there are too many producers and consumers. It's too much trouble to start one by one.
2. Problems found in the design
(1) The intention is to start the producers in all directories. Startup was unsuccessful. There are consistent dependencies between producers, and they must be started in order of dependencies. Why does this problem occur? Go to ask....
The best solution is to rely on three layers.
(2) Some environments do not need to start all,
For example, resources are limited and it is not suitable to start all services
Say someone just needs some services.
(3) Some configurations of different environments are different. Is it complicated to design.
(4) PID needs to be reserved
(5) Unable to detect whether the service starts normally
3. Trouble
(1) The setting and reading of the configuration, and other functions are completed. At present, I feel that this is the most troublesome.
two,
1, the reason,
Every time you pack scp and upload, you have to enter the server and start the service, which is very troublesome
2. Problems found in the design
(1) PID is required
(2) Document retention
(3) Configuration modification start
(4) Start up
3. Trouble