[ https://issues.apache.org/jira/browse/KUDU-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609152#comment-17609152 ]
ASF subversion and git services commented on KUDU-3319: ------------------------------------------------------- Commit e39411e086eeff6d77bcc640aaac34fdf8ca16df in kudu's branch refs/heads/master from Abhishek Chennaka [ https://gitbox.apache.org/repos/asf?p=kudu.git;h=e39411e08 ] [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 <ale...@apache.org> Reviewed-by: Alexey Serbin <ale...@apache.org> > Log Kudu notification/event ID during master startup > ---------------------------------------------------- > > Key: KUDU-3319 > URL: https://issues.apache.org/jira/browse/KUDU-3319 > Project: Kudu > Issue Type: Improvement > Components: hms, master > Reporter: Abhishek > Priority: Minor > > Currently during startup Kudu masters log the below during startup > {code:java} > I0601 18:24:05.250339 90422 catalog_manager.cc:1095] Loading latest processed > Hive Metastore notification log event ID...{code} > Would be helpful while debugging if we can log the actual ID retrieved. -- This message was sent by Atlassian Jira (v8.20.10#820010)