[jira] [Comment Edited] (HBASE-6089) SSH and AM.joinCluster causes Concurrent Modification exception.

2012-07-22 Thread Jonathan Hsieh (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420431#comment-13420431
 ] 

Jonathan Hsieh edited comment on HBASE-6089 at 7/23/12 4:52 AM:


Was not committed to 0.90

  was (Author: jmhsieh):
Was no in 0.90.7
  
 SSH and AM.joinCluster causes Concurrent Modification exception.
 

 Key: HBASE-6089
 URL: https://issues.apache.org/jira/browse/HBASE-6089
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.92.1, 0.94.0
Reporter: ramkrishna.s.vasudevan
Assignee: rajeshbabu
 Fix For: 0.92.2, 0.96.0, 0.94.1

 Attachments: HBASE-6089_92.patch, HBASE-6089_94.patch, 
 HBASE-6089_trunk.patch


 AM.regions map is parallely accessed in SSH and Master initialization leading 
 to ConcurrentModificationException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Comment Edited] (HBASE-6089) SSH and AM.joinCluster causes Concurrent Modification exception.

2012-05-30 Thread ramkrishna.s.vasudevan (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285541#comment-13285541
 ] 

ramkrishna.s.vasudevan edited comment on HBASE-6089 at 5/30/12 10:09 AM:
-

I was not clear in the previous comment.  Thinking again on this, there are 
some places where we wait for the this.regions to be populated.
{code}
synchronized(regions) {
  while(!regions.containsKey(regionInfo)) {
// We should receive a notification, but it's
//  better to have a timeout to recheck the condition here:
//  it lowers the impact of a race condition if any
regions.wait(100);
  }
{code}
When we need to update the this.servers also along with this.regions then we 
need to have some sync block.  I agree with Anoop here.

  was (Author: ram_krish):
Thinking again on this, there are some places where we wait for the 
this.regions to be populated.
{code}
{code}
  
 SSH and AM.joinCluster causes Concurrent Modification exception.
 

 Key: HBASE-6089
 URL: https://issues.apache.org/jira/browse/HBASE-6089
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.92.1, 0.94.0
Reporter: ramkrishna.s.vasudevan
Assignee: rajeshbabu
 Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1

 Attachments: HBASE-6089_92.patch, HBASE-6089_94.patch, 
 HBASE-6089_trunk.patch


 AM.regions map is parallely accessed in SSH and Master initialization leading 
 to ConcurrentModificationException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Comment Edited] (HBASE-6089) SSH and AM.joinCluster causes Concurrent Modification exception.

2012-05-29 Thread Zhihong Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284895#comment-13284895
 ] 

Zhihong Yu edited comment on HBASE-6089 at 5/29/12 6:03 PM:


Patch for trunk looks good.

  was (Author: zhi...@ebaysf.com):
Pstch for trunk looks good.
  
 SSH and AM.joinCluster causes Concurrent Modification exception.
 

 Key: HBASE-6089
 URL: https://issues.apache.org/jira/browse/HBASE-6089
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.92.1, 0.94.0
Reporter: ramkrishna.s.vasudevan
Assignee: rajeshbabu
 Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1

 Attachments: HBASE-6089_92.patch, HBASE-6089_94.patch, 
 HBASE-6089_trunk.patch


 AM.regions map is parallely accessed in SSH and Master initialization leading 
 to ConcurrentModificationException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira