Page History

...

...

Reasons for rebirth requests are:

• Triggered by user
  • A rebirth request for the Edge Node was manually triggered at MQTT Engine
    
• Message sequence number error

  • The message sequence number received was not in order 
    

    Tip
    In a Sparkplug compliant system, the combination of Group ID and Edge Node ID (the Sparkplug Edge Node Descriptor) that identifies the Edge Node must be unique.

     

    If there are two or more Transmitters with the same Sparkplug Edge Node Descriptor, data from these two transmitters will sent with the same topic resulting in the next message sequence number expected by the MQTT client being incorrect. As a result, the MQTT Client will mark the data as stale and request a rebirth from the transmitter. If you have multiple MQTT Clients subscribing to the namespace, this will also likely create a firestorm of rebirth requests across the system.

    
    

• Received a message for an edge node that is offline
  • A DDATA or An NDATA message was received from an Edge Node that is marked as Offline at MQTT Engine.
• Reordering sequence numbers
  
• Unknown metric
• Unable to initialize Edge Node
  • The message sequence number received was not in order after waiting the specified number of milliseconds after receiving an out of order message for the expected message to arrive.
• Unable to set Edge Node online
• NDATA before BIRTH
• DDATA before BIRTH
• Failed to find metric name from alias
  • The alias in the DATA message did not match any alias previously published in the BIRTH message 
• UDT tag doesn't exist
• Failed to add position tags in NBIRTH
• Unknown metric
• DDATA before BIRTH
  • An DDATA message was received from an Edge Node Device that is marked as Offline at MQTT Engine.
  Failed to add metric tags in NBIRTH