github.com/matrixorigin/matrixone@v0.7.0/etc/bootstrap-example2/README.md (about)

     1  # Bootstrap Example 2
     2  
     3  Assuming you are in MO's source directory.
     4  
     5  Build mo-service -
     6  
     7  ```
     8  make service
     9  ```
    10  Start 3 mo-service instances configured as Log Store instances and 1 as Data Node instance in 4 different terminals on the same machine.
    11  (**Note**: Currently, you need to start DN Store **first**.)
    12  ```
    13  ./mo-service -cfg etc/bootstrap-example/dn-node-1.toml
    14  ```
    15  ```
    16  ./mo-service -cfg etc/bootstrap-example/log-node-1.toml
    17  ```
    18  ```
    19  ./mo-service -cfg etc/bootstrap-example/log-node-2.toml
    20  ```
    21  ```
    22  ./mo-service -cfg etc/bootstrap-example/log-node-3.toml
    23  ```
    24  
    25  It takes several seconds to start each process on mac as the SSD is slow when invoking fsync(). After about 10-20 seconds, you should be able to see a minimal MO cluster with just 1 Data Service and 3 Log Service instances. On each Log Service instance, there is a HAKeeper replica and a Log Shard replica. 
    26  
    27  You should be able to see lots of logs on your terminals. "[00001:62146]" means Shard 1 ReplicaID 62146. You should be able to see log messages relate to replicas from both Shard 0 (HAKeeper), Shard 1 (regular Log shard) and Shard2 (DN shard) in each one of your terminals.
    28  
    29  To see how replicas are repaired in action, start another standby Log Service instance. 
    30  
    31  ```
    32  ./mo-service -cfg etc/bootstrap-example/log-node-4.toml
    33  ```
    34  
    35  then stop on of the first 3 Log Service instances by using CTRL+C or a kill signal. Wait for about 30 seconds and you should be able to see two replicas launched on the fourth Log Service instance launched above.