[ https://issues.apache.org/jira/browse/HBASE-23668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013501#comment-17013501 ]
Hudson commented on HBASE-23668: -------------------------------- Results for branch master [build #1595 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1595/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/master/1595//General_Nightly_Build_Report/] (x) {color:red}-1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1595//JDK8_Nightly_Build_Report_(Hadoop2)/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1595//JDK8_Nightly_Build_Report_(Hadoop3)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. (x) {color:red}-1 client integration test{color} --Failed when running client tests on top of Hadoop 2. [see log for details|https://builds.apache.org/job/HBase%20Nightly/job/master/1595//artifact/output-integration/hadoop-2.log]. (note that this means we didn't run on Hadoop 3) > Master log start filling with "Flush journal status" messages > ------------------------------------------------------------- > > Key: HBASE-23668 > URL: https://issues.apache.org/jira/browse/HBASE-23668 > Project: HBase > Issue Type: Improvement > Components: proc-v2, RegionProcedureStore > Reporter: Michael Stack > Assignee: Michael Stack > Priority: Major > Fix For: 3.0.0, 2.3.0 > > > Takes a while to get into this condition. Not each to tell how because all > logs have rolled off and I only have logs filled w/ below: > {code} > 2020-01-09 07:01:01,723 DEBUG org.apache.hadoop.hbase.regionserver.HRegion: > Flush status journal: > Acquiring readlock on region at 1578553261723 > Flush successful flush result:CANNOT_FLUSH_MEMSTORE_EMPTY, > failureReason:Nothing to flush,flush seq id45226854 at 1578553261723 > 2020-01-09 07:01:01,723 DEBUG org.apache.hadoop.hbase.regionserver.HRegion: > Flush status journal: > Acquiring readlock on region at 1578553261723 > Flush successful flush result:CANNOT_FLUSH_MEMSTORE_EMPTY, > failureReason:Nothing to flush,flush seq id45226855 at 1578553261723 > 2020-01-09 07:01:01,723 DEBUG org.apache.hadoop.hbase.regionserver.HRegion: > Flush status journal: > Acquiring readlock on region at 1578553261723 > Flush successful flush result:CANNOT_FLUSH_MEMSTORE_EMPTY, > failureReason:Nothing to flush,flush seq id45226856 at 1578553261723 > 2020-01-09 07:01:01,723 DEBUG org.apache.hadoop.hbase.regionserver.HRegion: > Flush status journal: > Acquiring readlock on region at 1578553261723 > Flush successful flush result:CANNOT_FLUSH_MEMSTORE_EMPTY, > failureReason:Nothing to flush,flush seq id45226857 at 1578553261723 > {code} > ... I added the printing of flushresult... i.e. cannot flush because store is > empty. > Digging. -- This message was sent by Atlassian Jira (v8.3.4#803005)