[
https://issues.apache.org/jira/browse/HBASE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903880#comment-13903880
]
Feng Honghua commented on HBASE-10557:
--------------------------------------
bq.It seems this code use (a) some cleanup and (b) some Javadoc explaining what
Feng just tracked down.
Yes, only one thing is that the place throwing exception and the place
catching/handling it are so far apart...
[~lhofhansl], would you take some time to review and confirm HBASE-10556? It's
a similar issue but looks like not properly handled by current implementation.
Thanks:-)
> DroppedSnapshotException is not handled properly for flush triggered by
> hlog-replay and non-abort region close
> --------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-10557
> URL: https://issues.apache.org/jira/browse/HBASE-10557
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: Feng Honghua
> Assignee: Feng Honghua
> Priority: Critical
>
> Flush triggered by hlog-replay(replayRecoveredEdits) and
> region-close(non-abort close) get processed directly by region without
> putting flush entry into flushQueue, hence not handled by MemStoreFlusher, So
> DroppedSnapshotException emitted from internalFlushcache is not handled
> properly
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
