[
https://issues.apache.org/jira/browse/HBASE-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464107#comment-13464107
]
stack commented on HBASE-6679:
------------------------------
bq. Yes.. but that still could be exposed to the problems of memory
inconsistencies when multiple threads are accessing the object in
unsynchronized/non-volatile ways, no?
We swap in the new list when compaction completes. I suppose we could make the
reference volatile so all threads catch the update.
But you can't see how the two threads can run concurrently? (not to say it not
possible)
I'd say close this issue if you don't have the logs to disprove it a case of
dbl-assign, a more plausible explanation to my mind?
Good on you Deva.
> RegionServer aborts due to race between compaction and split
> ------------------------------------------------------------
>
> Key: HBASE-6679
> URL: https://issues.apache.org/jira/browse/HBASE-6679
> Project: HBase
> Issue Type: Bug
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.92.3
>
> Attachments: rs-crash-parallel-compact-split.log
>
>
> In our nightlies, we have seen RS aborts due to compaction and split racing.
> Original parent file gets deleted after the compaction, and hence, the
> daughters don't find the parent data file. The RS kills itself when this
> happens. Will attach a snippet of the relevant RS logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
