[
https://issues.apache.org/jira/browse/HBASE-26675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481858#comment-17481858
]
Hudson commented on HBASE-26675:
--------------------------------
Results for branch master
[build #501 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/501/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/501/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/501/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/501/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Data race on Compactor.writer
> -----------------------------
>
> Key: HBASE-26675
> URL: https://issues.apache.org/jira/browse/HBASE-26675
> Project: HBase
> Issue Type: Bug
> Components: Compaction
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.6.0, 3.0.0-alpha-3
>
>
> In Compactor.getCompactionTargets, we use synchronized on the writer instance
> but it does not help resolve the data race problem, because in other places
> we do not use synchronized...
> And since it is not a big deal to the upper layer an old snapshot, we could
> just make the writer instance volatile and use it directly in the method,
> just make sure we always use the same instance in the method, i.e, assign it
> to a local var first.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
