[
https://issues.apache.org/jira/browse/HBASE-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933094#action_12933094
]
Todd Lipcon commented on HBASE-3243:
------------------------------------
bq. Looking at this more, I'm not sure synchronization is the issue here
because TreeMap appears to only be not thread-safe when there are mutations.
The two critical pieces of code where a conflict could happen are where we read
the server a region is assigned to, and where we set the server a region is
assigned to
What about removals? I thought I saw a couple places with remove() that were
unsynchronized. Will take a look at your patch momentarily.
bq. This is very weird. Can you put up the full logs somewhere
Yep, will upload them here, it's just fake data, nothing secret.
> Disable Table closed region on wrong host
> -----------------------------------------
>
> Key: HBASE-3243
> URL: https://issues.apache.org/jira/browse/HBASE-3243
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.90.0
> Reporter: Todd Lipcon
> Priority: Blocker
> Fix For: 0.90.0
>
> Attachments: HBASE-3243-v1.patch
>
>
> I ran some YCSB benchmarks which resulted in about 150 regions worth of data
> overnight. Then I disabled the table, and the master for some reason closed
> one region on the wrong server. The server ignored this, but the region
> remained open on a different server, which later flipped out when it tried to
> flush due to hlog accumulation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
