Browse Source
Since only the active controller is performing the dual-write to ZK during a migration, it should be the only controller to report the ZkWriteBehindLag metric. Currently, if the controller fails over during a migration, the previous active controller will incorrectly report its last value for ZkWriteBehindLag forever. Instead, it should report zero. Reviewers: Colin P. McCabe <cmccabe@apache.org>, David Arthur <mumrah@gmail.com>pull/14569/head
mannoopj
1 year ago
committed by
GitHub
2 changed files with 18 additions and 2 deletions
Loading…
Reference in new issue