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
Describe the bug
I have vm setup with two insert nodes and one storage node.
Today i've shutdown storage node and after starting it back get not all of my points from prometheus
To Reproduce
prometheus -1-> vm_balancer -2-> vm_insert -3- > vm_storage
It has been appeared that vminsert could drop pending rows when all the vmstorage nodes were unavailable. This should be fixed in the commit 4d70a81 . This commit will be included in the next release of cluster version of VictoriaMetrics.
After the commit 4d70a81vminsert should always return 503 error to Prometheus when it cannot write data to vmstorage, so Prometheus could enable retry mechanism until vmstorage are recovered. This should prevent from data loss on temporary unavailability of all the vmstorage nodes in the cluster.
Closing the issue as fixed. @freeseacher , feel free re-opening it if VictoriaMetrics v1.32.7 or newer release continues dropping data when all the vmstorage nodes are unavailable.
Describe the bug
I have vm setup with two insert nodes and one storage node.
Today i've shutdown storage node and after starting it back get not all of my points from prometheus
To Reproduce
prometheus -1-> vm_balancer -2-> vm_insert -3- > vm_storage
1
vm_balancer is
vm_insert is
vminsert-20200117-162442-tags-v1.32.5-cluster-0-g29d21259
vm-storage is vmstorage-20200117-162449-tags-v1.32.5-cluster-0-g29d21259
Expected behavior
on storage node up all points from prometheus appered in vm_storage.
Screenshots
Additional context
vm_insert logs
Promtheus
The text was updated successfully, but these errors were encountered: