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

Cluster freshness should fail if no single partition succeeds #58

Merged

Conversation

jyates
Copy link
Contributor

@jyates jyates commented Jun 28, 2022

Across all the partitions for all topics for all consumers for a given
cluster, if we succeed at reading the freshness for at least one of
the consumers then the cluster freshness succeeds. Without this, if
none the consumers could be evaluated successfully then the cluster
would still be marked successful, but that often indicated an
incorrectly configured cluster. However, if we are able to read even
a single partition, then we can reach the cluster. Maybe its a transient
so we should be allowed a next round to try to get more successes.

Addresses #51

@jyates jyates force-pushed the 51-fail-freshness-if-all-partitions-fail branch from b23e264 to fb7cc52 Compare June 28, 2022 12:58
@@ -281,7 +283,37 @@ private ListenableFuture<String> measureCluster(Burrow.ClusterClient client) {
// if all the consumer measurements succeed, then we return the cluster name
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if all the consumer measurements succeed -> if at least one consumer measurement succeeds?

Across all the partitions for all topics for all consumers for a given
cluster, if we succeed at reading the freshness for at least one of
the consumers then the cluster freshness succeeds. Without this, if
none the consumers could be evaluated successfully then the cluster
would still be marked successful, but that often indicated an
incorrectly configured cluster. However, if we are able to read even
a single partition, then we can reach the cluster. Maybe its a transient
so we should be allowed a next round to try to get more successes.

Addresses teslamotors#51
@jyates jyates force-pushed the 51-fail-freshness-if-all-partitions-fail branch from fb7cc52 to 70afff1 Compare June 29, 2022 09:26
@jyates jyates merged commit 491b1b8 into teslamotors:master Jun 29, 2022
@jyates jyates deleted the 51-fail-freshness-if-all-partitions-fail branch June 29, 2022 09:35
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.

3 participants