You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary - Some messages exchanged between services are lost, or duplicated
Bug Details :
What? - In our case, the sensor proxy service is logging data which should be processed by the data processing service. Some of those messages seem to be getting lost. This was observed by a missing message in the mobsos database. Interestingly enough, the following message was stored twice.
Where? - This has been observed when the proxy service is monitoring a message (SERVICE_CUSTOM_MESSAGE_1 and SERVICE_CUSTOM_MESSAGE_2). The sensor proxy is deployed on the cluster in the sensor-proxy namespace and connected to the main las2peer network.
When?/How often? - This bug appears sporadically affecting about 1% of the monitored messages.
How?/Current state - There is a las2peer message with message id -4790160650064024141 and timestamp 1636379185354 missing.
MESSAGE with id 8904867 and MESSAGE with id 8904872 are identical. The respective messages can be looked up under the MESSAGE table in the mobsos database of the main network.
The text was updated successfully, but these errors were encountered:
SERVICE_CUSTOM_MESSAGE_1
andSERVICE_CUSTOM_MESSAGE_2
). The sensor proxy is deployed on the cluster in the sensor-proxy namespace and connected to the main las2peer network.MESSAGE with id 8904867 and MESSAGE with id 8904872 are identical. The respective messages can be looked up under the MESSAGE table in the mobsos database of the main network.
The text was updated successfully, but these errors were encountered: