This is an automated email from the ASF dual-hosted git repository. granthenke pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/kudu.git
commit 60db4aeea0c47e6d7b7557b850cf6378b5ad67ce Author: Grant Henke <[email protected]> AuthorDate: Wed Jul 15 15:35:48 2020 -0500 [hms] Reduce noisy logging on non-leader masters. Recently while reviewing kudu master logs in a cluster with HMS sync enabled I noticed many occurances of the below log on the follower masters: I0323 20:38:12.824517 6245 hms_notification_log_listener.cc:227] Skipping Hive Metastore notification log poll: Illegal state: Not the leader. … I lowered the log level so it would not be logged in the common case given this is frequent, expected, and ignored. Change-Id: I0fa308727a71f51ded780eb97d9cdc87cb6f9069 Reviewed-on: http://gerrit.cloudera.org:8080/16203 Reviewed-by: Andrew Wong <[email protected]> Tested-by: Kudu Jenkins Reviewed-by: Attila Bukor <[email protected]> --- src/kudu/master/hms_notification_log_listener.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/kudu/master/hms_notification_log_listener.cc b/src/kudu/master/hms_notification_log_listener.cc index cbd14bf..517a489 100644 --- a/src/kudu/master/hms_notification_log_listener.cc +++ b/src/kudu/master/hms_notification_log_listener.cc @@ -227,7 +227,7 @@ Status HmsNotificationLogListenerTask::Poll() { // This method calls the catalog manager directly, so ensure the leader lock is held. CatalogManager::ScopedLeaderSharedLock l(catalog_manager_); if (!l.first_failed_status().ok()) { - LOG(INFO) << "Skipping Hive Metastore notification log poll: " + VLOG(1) << "Skipping Hive Metastore notification log poll: " << l.first_failed_status().ToString(); return Status::OK(); }
