[
https://issues.apache.org/jira/browse/HBASE-16696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529120#comment-15529120
]
ramkrishna.s.vasudevan commented on HBASE-16696:
------------------------------------------------
I think it is better to go with patch 1. The failures in last QA run was due to
removing those changes wrt context==null I believe. With _2 version of the
patch I could see those tests to hang TestMultiRespectsLimits and
TestGlobalMemStoreSize.
But with the first version of the patch those tests pass.
I prefer the first patch for commit where the exception was considered in
finally block. Ping!!!
> After HBASE-16604 - does not release blocks in case of scanner exception
> ------------------------------------------------------------------------
>
> Key: HBASE-16696
> URL: https://issues.apache.org/jira/browse/HBASE-16696
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-16696.patch, HBASE-16696.patch,
> HBASE-16696_1.patch, HBASE-16696_2.patch
>
>
> TestBlockEvictionFromClient consistently fails in master branch.
> From existing Jenkins builds, looks like this started with build 1639.
> See attached Jenkins console logs.
> Pls refer to this comment
> https://issues.apache.org/jira/secure/EditComment!default.jspa?id=13004009&commentId=15522451
> for the reason for the test failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
