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

Hudson commented on HBASE-25643:
--------------------------------

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

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/240/General_20Nightly_20Build_20Report/]






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


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/240/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}


> The delayed FlushRegionEntry should be removed when we need a non-delayed one
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-25643
>                 URL: https://issues.apache.org/jira/browse/HBASE-25643
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Zheng Wang
>            Assignee: Zheng Wang
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.5.0
>
>
> The regionserver periodically check all the regions, if one not flushed for 
> long time, then it will create a delayed FlushRegionEntry, the delay range is 
> 0~300s.
> During the delay time, if many data are written to the region suddenly, we 
> can not do the flush immediately due to the existing one in regionsInQueue, 
> then the RegionTooBusyException will occur.
> It is better to improve the logic here, that the delayed entry should be 
> replaced by the non-delayed one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to