TIPC Cluster5

• Link

  TIPC cluster It consists of nodes interconnected by links . Nodes can be physical processors 、 Virtual machine or network namespace , for example , With Docker The form of the container . The link constitutes a reliable packet transmission service , Sometimes called “L2.5” Data link layer .

  1、 It ensures the transmission and sequencing of all packets .
  2、 It acts as a relay for connections between nodes , And track these connections .
  3、 When all contacts with peer nodes are lost , All sockets connected to this peer node will be notified , So that they can disconnect .
  4、 Each endpoint tracks the address binding of the peer node in the local copy of the binding table .
  5、 When the contact with the peer node is lost , All bindings from this peer node will be cleared , And send service tracking events to all matching subscribers .
  
  1、 When there is no regular packet communication , Every link goes through probing/heartbeats Conduct active monitoring .
  2、 The fault detection tolerance can be configured as 50 ms To 30 second ,- The default setting is 1.5 second .
  3、 For performance and redundancy reasons , Each node pair can establish two links on a separate network interface .
  4、 Link pairs can be configured as load sharing or active standby .
  5、 If a link fails , Then the remaining links （ If any ） Perform interference free failover .

• Cluster Membership

  One cluster have 32 position cluster identification , It decided cluster Set up .

  1、 If you need anything different from the default （ for example , If there are multiple clusters on the same subnet ）, Then the user can assign a cluster ID .
  2、 All nodes using the same cluster ID will be linked .
  3、 Neighbors found through UDP Multicast or L2 radio broadcast （ If available ） perform .
  4、 If there is a lack of broadcasting in the infrastructure / Multicast support , Can be configured explicitly IP Address execution discovery
  
  Each node has a cluster Unique node ID .

  1、 stay Linux 4.17 In the previous version , This is a 32 Structured address of bit , Must be set by the user .
  2、 In later versions , It's a 128 Bit fields , No internal structure or restrictions .
  3、 By default , This identification is based on MAC or IP Address settings .
  4、 It can also be set by the user , for example , Based on hostname or UUID.
  5、 Identification is internally hashed as a guarantee of uniqueness 32 Bit node address , This address becomes the node address used by the Protocol .
  6、 These two identification formats are compatible , It can be used in the same cluster .

• Cluster Scalability

  since Linux 4.7 since ,TIPC Provides a unique 、 Patent pending 、 Automatic adaptive hierarchical neighbor monitoring algorithm . This makes it possible to build the most 1000 A complete grid cluster of nodes is possible , The fault discovery time is 1.5 second , In smaller clusters , It can shorten a lot .