[
https://issues.apache.org/jira/browse/KUDU-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165871#comment-17165871
]
Grant Henke commented on KUDU-3037:
-----------------------------------
The logging issue has been addressed in
https://github.com/apache/kudu/commit/60db4aeea0c47e6d7b7557b850cf6378b5ad67ce
Leaving this open so we can look at disabling the listener in followers as a
more complete solution.
> HMS notification log listener runs in follower masters
> ------------------------------------------------------
>
> Key: KUDU-3037
> URL: https://issues.apache.org/jira/browse/KUDU-3037
> Project: Kudu
> Issue Type: Improvement
> Components: hms, master
> Affects Versions: 1.11.1
> Reporter: Adar Dembo
> Priority: Major
> Labels: trivial
>
> Besides wasting resources, this also emits the same log message every second:
> {noformat}
> I0108 21:05:07.748235 1443 hms_notification_log_listener.cc:227] Skipping
> Hive Metastore notification log poll: Illegal state: Not the leader. Local
> UUID: c77bd888023149729481b7fd041b5c83, Raft Consensus state: current_term: 6
> committed_config { opid_index: -1 OBSOLETE_local: false peers {
> permanent_uuid: "12e9881f0c094a38b83c3b00f71a0ef1" member_type: VOTER
> last_known_addr { host: "127.0.60.126" port: 43289 } } peers {
> permanent_uuid: "c77bd888023149729481b7fd041b5c83" member_type: VOTER
> last_known_addr { host: "127.0.60.125" port: 38761 } } peers {
> permanent_uuid: "c362d38459074310a6fbd3da10153538" member_type: VOTER
> last_known_addr { host: "127.0.60.124" port: 34903 } } }
> {noformat}
> We could throttle the log message, though perhaps the more complete solution
> is to only activate the log listener in the leader master.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
