Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
2.4.16, 2.5.3
-
None
-
None
-
None
Description
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.
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
Attachments
Issue Links
- is duplicated by
-
HBASE-27626 Suppress noisy logging in client.ConnectionImplementation
- Resolved
- is related to
-
HBASE-27498 Observed lot of threads blocked in ConnectionImplementation.getKeepAliveMasterService
- Resolved