On 14/11/19 14:54 +0100, Jan Pokorný wrote: > On 13/11/19 17:30 -0600, Ken Gaillot wrote: >> A longstanding pain point in the logs has been improved. Whenever the >> scheduler processes resource history, it logs a warning for any >> failures it finds, regardless of whether they are new or old, which can >> confuse anyone reading the logs. Now, the log will contain the time of >> the failure, so it's obvious whether you're seeing the same event or >> not. > > Just curious, how sensitive is this to time shifts, e.g. timezone > related? If it is (human/machine can be unable to match the same event > reported back then and now in a straightforward way, for say time zone > transition in between), considering some sort of rather unique > identifier would be a more systemic approach for an event matching > in an invariant manner, but then would we need some notion of > monotonous cluster-wide sequence ordering? ^^^^^^^^^^
Sorry, monotonic (i.e. in a mathematical sense) -- Jan (Poki)
pgpbC2dR0AYgT.pgp
Description: PGP signature
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
