You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "wenfeiyi666 (Jira)" <ji...@apache.org> on 2020/07/17 07:48:00 UTC
[jira] [Commented] (HBASE-24745) 'Failed report transition' logs
too often
[ https://issues.apache.org/jira/browse/HBASE-24745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159751#comment-17159751 ]
wenfeiyi666 commented on HBASE-24745:
-------------------------------------
[~stack], I add a UT, but this problem did not occur. Can you give more detailed logs
> 'Failed report transition' logs too often
> -----------------------------------------
>
> Key: HBASE-24745
> URL: https://issues.apache.org/jira/browse/HBASE-24745
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.3.0
> Reporter: Michael Stack
> Assignee: wenfeiyi666
> Priority: Minor
>
> The parent issue fixed a backoff that was too aggressive. Now I notice we try too much. Saw 9k logs in 17 seconds of the below type...
> {code:java}
> 2020-07-15 14:36:23,104 INFO org.apache.hadoop.hbase.regionserver.HRegionServer: Failed report transition server { host_name: "X.example.org" port: 16020 start_code: 1594823099666 } transition { transition_ code: CLOSED region_info { region_id: 1594814749475 table_name { namespace: "default" qualifier: "IntegrationTestBigLinkedList" } start_key: "\"\"\"\"\"\"\" " end_key: "#Q\352\f\003" offline: false split: false replica_id: 0 } proc_id: 81545 }; retry (#8888) after 200805ms delay (Master is coming online...).
> {code}
> The delay doesn't seem correct or respected.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)