Bryan Beaudreault created HBASE-28363:
-----------------------------------------
Summary: Noisy exception from FlushRegionProcedure when result is
CANNOT_FLUSH
Key: HBASE-28363
URL: https://issues.apache.org/jira/browse/HBASE-28363
Project: HBase
Issue Type: Bug
Reporter: Bryan Beaudreault
Running ITBLL with chaos monkey in HBASE-28233. I noticed lots of exceptions:
{code:java}
[RS_FLUSH_OPERATIONS-regionserver/test-host:60020-1
{event_type=RS_FLUSH_REGIONS, pid=741536}] ERROR
org.apache.hadoop.hbase.regionserver.handler.RSProcedureHandler: pid=741536
java.io.IOException: Unable to complete flush {ENCODED =>
371d2ba6875913542893642c94634226, NAME =>
'IntegrationTestBigLinkedList,-\x82\xD8-\x82\xD8-\x80,1707761077516.371d2ba6875913542893642c94634226.',
STARTKEY =
> '-\x82\xD8-\x82\xD8-\x80', ENDKEY => '33333330'}
at
org.apache.hadoop.hbase.regionserver.FlushRegionCallable.doCall(FlushRegionCallable.java:61)
~[hbase-server-2.6-hubspot-SNAPSHOT.jar:2.6-hubspot-SNAPSHOT]
at
org.apache.hadoop.hbase.procedure2.BaseRSProcedureCallable.call(BaseRSProcedureCallable.java:35)
~[hbase-server-2.6-hubspot-SNAPSHOT.jar:2.6-hubspot-SNAPSHOT]
at
org.apache.hadoop.hbase.procedure2.BaseRSProcedureCallable.call(BaseRSProcedureCallable.java:23)
~[hbase-server-2.6-hubspot-SNAPSHOT.jar:2.6-hubspot-SNAPSHOT]
at
org.apache.hadoop.hbase.regionserver.handler.RSProcedureHandler.process(RSProcedureHandler.java:51)
~[hbase-server-2.6-hubspot-SNAPSHOT.jar:2.6-hubspot-SNAPSHOT]
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
~[hbase-server-2.6-hubspot-SNAPSHOT.jar:2.6-hubspot-SNAPSHOT]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
~[?:?]
at java.lang.Thread.run(Thread.java:840) ~[?:?] {code}
I took a look at the HRegion.flushcache code, and there are 3 reasons for
CANNOT_FLUSH. All only print at debug log level and none look like actual
errors.
I think we shouldn't throw an exception here, or at least should downgrade to
debug. It looks like a problem, but isn't (i dont think).
cc [~frostruan]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
