[
https://issues.apache.org/jira/browse/HBASE-20204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471101#comment-16471101
]
Hudson commented on HBASE-20204:
--------------------------------
Results for branch branch-1.4
[build #316 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/316/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/316//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/316//JDK7_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/branch-1.4/316//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Add locking to RefreshFileConnections in BucketCache
> ----------------------------------------------------
>
> Key: HBASE-20204
> URL: https://issues.apache.org/jira/browse/HBASE-20204
> Project: HBase
> Issue Type: Bug
> Components: BucketCache
> Affects Versions: 1.4.3, 2.0.0
> Reporter: Zach York
> Assignee: Zach York
> Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.4.5
>
> Attachments: HBASE-20204.master.001.patch,
> HBASE-20204.master.002.patch, HBASE-20204.master.003.patch,
> HBASE-20204.master.004.patch
>
>
> This is a follow-up to HBASE-20141 where [~anoop.hbase] suggested adding
> locking for refreshing channels.
> I have also seen this become an issue when a RS has to abort and it locks on
> trying to flush out the remaining data to the cache (since cache on write was
> turned on).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
