problem: confusing upstream lag numbers in log

This commit is contained in:
Igor Artamonov
2021-12-18 19:43:40 -05:00
parent 6cbb3a6fe1
commit 2f829fab98

View File

@@ -295,7 +295,17 @@ abstract class Multistream(
.groupBy { it }
.map { "${it.key.name}/${it.value.size}" }
.joinToString(",")
val lag = upstreams.map { it.getLag() }
val lag = upstreams
.map {
// by default, when no lag is available it uses Long.MAX_VALUE, and it doesn't make sense to print
// status with such value. use NA (as Not Available) instead
val value = it.getLag()
if (value == Long.MAX_VALUE) {
"NA"
} else {
value.toString()
}
}
.joinToString(", ")
val weak = upstreams
.filter { it.getStatus() != UpstreamAvailability.OK }