commit e39411e086eeff6d77bcc640aaac34fdf8ca16df
author Abhishek Chennaka <achennaka@cloudera.com> Wed Aug 17 17:40:26 2022 -0400
committer Alexey Serbin <alexey@apache.org> Sun Sep 25 12:32:33 2022 +0000
tree a8fda1a8dd457a2c58ff84eee5fd0fafb31250bc
parent 0c71a070727bc0c645eed1d661822c9286fe461f

[master] KUDU-3322 / KUDU-3319 HMS event logging

It would be useful to have additional logging in cases where HMS
notification events have to be analyzed from Kudu side. The Jiras
have more context on the reasoning behind this but this patch adds
* an INFO level log which shows the last processed HMS event id during
startup and
* an ERROR log if the latest event id from HMS is less than
the last seen event id from the master. Was hesitant on crashing the
master and chose to log an ERROR as in the case an out of order event
id received from HMS might lead to unnecessary crash of the Kudu
master.

Change-Id: I242c9cedf170ed621867b905f1cb1875347d5887
Reviewed-on: http://gerrit.cloudera.org:8080/18866
Tested-by: Alexey Serbin <alexey@apache.org>
Reviewed-by: Alexey Serbin <alexey@apache.org>