[IOTDB-3424] avoid running duplicated IotDB server/node

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Others
• Labels: pull-request-available
• Assignee: Bo Zhang
• Reporter: Bo Zhang
• Created: 08/Jun/22 03:30
• Updated: 11/Aug/22 09:16
• Resolved: 13/Jun/22 06:25

Description

Backgroud: 

1) Sometimes, customers wrongly run 2 IoTDB servers porcess from same directory at same time, which can cause Tsfiles' damage.

2)  Another JIRA:  https://issues.apache.org/jira/browse/IOTDB-3306 has done some change.  IOTDB-3306's code change let rpc-server starting as early as possible, so that the second IoTDB server proccess can detect listening port conflict before changing Tsfile and then exit.

3) But  IOTDB-3306's fix will let IoTDB server open rpc service too early, which can casue some client task failure.

=========================================================================

After discussion with HouHaoNan, we think there is better solution than IOTDB-3306's fix.  New solution is to change start-server.sh to detect whether 1 IoTDB server porcess from same directory has existed.

 

Issue Links

• relates to: IOTDB-3306 "io task meets error" is not handled correctly
• links to: GitHub Pull Request #6200