Open hernandezc1 opened 5 days ago
After starting the VM and manually going through its startup script, I see that the consumer was able to subscribe to the topic successfully. After a few minutes, the consumer's nodes disconnect.
It seems that this issue is associated with the version of Confluent that the VM is using (v7.4), as other developers have seen similar log messages using the same version (see this Stack Overflow discussion)
A review of the
lvk-alerts
Pub/Sub topic’s metrics reveals that alerts stopped publishing unexpectedly to the topic after August 12th, at around 2:30pm. Thelvk-alerts
topic in theavid-heading-329016
project, however, continues to publish alerts to date (I was using this project to test the changes for PR #232). The Logs Explorer displays the following logs from the time-frame of 8/10/2024 through (8/13/2024):
The log on August 10th implies that the VM instance’s underlying hardware underwent maintenance, and was moved to another host as a result (see Live migration process during maintenance events for more information). However, Google’s documentation states that “live migration lets Google Cloud perform maintenance without interrupting a workload, rebooting a VM, or modifying any of the VM's properties, such as IP addresses, metadata, block storage data, application state, and network settings.” At the moment, it is not clear to me what caused alerts to stop being published.
Here is a visualization of the Pub/Sub metrics for
lvk-alerts
inardent-cycling-243415
:I will continue to investigate this and update this issue as I discover more information.