Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix cloned resource collection once and for all #194

Conversation

stefanotorresi
Copy link
Member

@stefanotorresi stefanotorresi commented May 27, 2021

follow-up of #191, fixes #193

This is a more generic solution which keeps the tracking of stopped resources even when they are cloned (#191 was a quick and dirty solution that removed the tracking altogether, and only for the clusterfs RA).

Pacemaker Clone Resources appear multiple times in crm_mon; since the main discriminator field is the node, and that's missing when a resource is stopped, the cloned and stopped entries will appear multiple times in the crm_mon output, with the exact same fields and values: this is a problem for the Prometheus SDK, which doesn't expect duplicate metrics over the course of a single collection cycle.

Collaterally, this PR also removes the download make target, which was a vestigial thing required when using old Go versions.

@stefanotorresi stefanotorresi merged commit 96264e8 into ClusterLabs:master May 28, 2021
@stefanotorresi stefanotorresi deleted the fix-cloned-resources-collection-once-and-for-all branch May 28, 2021 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error when disabled all cluster nodes
1 participant