[ 
https://issues.apache.org/jira/browse/HBASE-27626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686819#comment-17686819
 ] 

Hudson commented on HBASE-27626:
--------------------------------

Results for branch branch-2
        [build #742 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/742/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/742/General_20Nightly_20Build_20Report/]


(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/742/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/742/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/742/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Suppress noisy logging in client.ConnectionImplementation
> ---------------------------------------------------------
>
>                 Key: HBASE-27626
>                 URL: https://issues.apache.org/jira/browse/HBASE-27626
>             Project: HBase
>          Issue Type: Task
>          Components: logging
>    Affects Versions: 2.4.16, 2.5.3
>            Reporter: Nihal Jain
>            Assignee: Nihal Jain
>            Priority: Minor
>             Fix For: 2.6.0, 2.4.17, 2.5.4
>
>
> _client.ConnectionImplementation_ logs a lot at INFO level:
> {code:java}
> hbase:001:0> restore_snapshot  'tableSnapshot'
> 2023-02-09 05:15:35,538 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:35,538 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:36,599 INFO  [main] client.HBaseAdmin: Taking 
> restore-failsafe snapshot: hbase-failsafe-tableSnapshot-1675919736599
> 2023-02-09 05:15:36,608 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:36,608 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> 2023-02-09 05:15:36,806 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:36,806 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> 2023-02-09 05:15:37,026 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:37,026 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> 2023-02-09 05:15:37,334 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:37,334 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> 2023-02-09 05:15:37,341 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:37,342 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> 2023-02-09 05:15:37,413 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:37,413 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> 2023-02-09 05:15:37,534 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:37,535 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> 2023-02-09 05:15:37,742 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:37,742 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> 2023-02-09 05:15:38,055 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:38,056 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> 2023-02-09 05:15:38,561 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:38,561 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> 2023-02-09 05:15:38,568 INFO  [main] client.HBaseAdmin: Operation: MODIFY, 
> Table Name: nj:testImport, procId: 392 completed
> 2023-02-09 05:15:38,568 INFO  [main] client.HBaseAdmin: Deleting 
> restore-failsafe snapshot: hbase-failsafe-tableSnapshot-1675919736599
> 2023-02-09 05:15:38,570 INFO  [main] client.ConnectionImplementation: Getting 
> master connection state from TTL Cache
> 2023-02-09 05:15:38,570 INFO  [main] client.ConnectionImplementation: Getting 
> master state using rpc call
> Took 3.1595 seconds
> {code}
> We should log these lines in TRACE level.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to