[ https://issues.apache.org/jira/browse/HBASE-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964926#action_12964926 ]
Jonathan Gray commented on HBASE-3243: -------------------------------------- Yes. That was wrong, we never use this.servers as a lock, we always manipulate this.regions and this.servers under the this.regions lock. The removal from regionPlans was just moved underneath it, I didn't take that part out. It's in the next chunk of the diff. > 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-logs.tar.bz2, HBASE-3243-v1.patch, hri.diff > > > 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.