problem: confusing upstream lag numbers in log
This commit is contained in:
@@ -295,7 +295,17 @@ abstract class Multistream(
|
|||||||
.groupBy { it }
|
.groupBy { it }
|
||||||
.map { "${it.key.name}/${it.value.size}" }
|
.map { "${it.key.name}/${it.value.size}" }
|
||||||
.joinToString(",")
|
.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(", ")
|
.joinToString(", ")
|
||||||
val weak = upstreams
|
val weak = upstreams
|
||||||
.filter { it.getStatus() != UpstreamAvailability.OK }
|
.filter { it.getStatus() != UpstreamAvailability.OK }
|
||||||
|
|||||||
Reference in New Issue
Block a user