In RoutingMasterCore, the "table_update_interval_ms" parameter defines the maximum amount of time that the RoutingMaster should allow between table updates. It should be possible, however, to use some combination of the tokens and the routing table acks to determine what the system rate is, and/or whether sufficient routing information is present in the system, regardless of the current table interval. The expected rate should change slowly, however, so that dataflow issues can still be detected and reported in the RoutingMaster.
This issue has been migrated from https://cdcvs.fnal.gov/redmine/issues/20764 (FNAL account required) Originally created by @eflumerf on 2018-09-06 19:20:24
In RoutingMasterCore, the "table_update_interval_ms" parameter defines the maximum amount of time that the RoutingMaster should allow between table updates. It should be possible, however, to use some combination of the tokens and the routing table acks to determine what the system rate is, and/or whether sufficient routing information is present in the system, regardless of the current table interval. The expected rate should change slowly, however, so that dataflow issues can still be detected and reported in the RoutingMaster.