You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Tak-Lon (Stephen) Wu (Jira)" <ji...@apache.org> on 2023/02/09 16:11:00 UTC
[jira] [Resolved] (HBASE-27603) Optimize INFO message after HBASE-27498
[ https://issues.apache.org/jira/browse/HBASE-27603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tak-Lon (Stephen) Wu resolved HBASE-27603.
------------------------------------------
Resolution: Duplicate
> Optimize INFO message after HBASE-27498
> ---------------------------------------
>
> Key: HBASE-27603
> URL: https://issues.apache.org/jira/browse/HBASE-27603
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.4.16, 2.5.3
> Reporter: Tak-Lon (Stephen) Wu
> Assignee: Tak-Lon (Stephen) Wu
> Priority: Major
>
> During the RC vote of 2.4.16 and 2.5.3, I found the below message should be removed or hidden from the connection operation.
> {code}
> 2023-01-31T15:19:03,890 INFO [main] client.ConnectionImplementation: Getting master connection state from TTL Cache
> 2023-01-31T15:19:03,891 INFO [main] client.ConnectionImplementation: Getting master state using rpc call
> 2023-01-31T15:19:03,997 INFO [main] client.ConnectionImplementation: Getting master connection state from TTL Cache
> 2023-01-31T15:19:03,997 INFO [main] client.ConnectionImplementation: Getting master state using rpc call
> 2023-01-31T15:19:04,201 INFO [main] client.ConnectionImplementation: Getting master connection state from TTL Cache
> 2023-01-31T15:19:04,202 INFO [main] client.ConnectionImplementation: Getting master state using rpc call
> 2023-01-31T15:19:04,508 INFO [main] client.ConnectionImplementation: Getting master connection state from TTL Cache
> 2023-01-31T15:19:04,508 INFO [main] client.ConnectionImplementation: Getting master state using rpc call
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)