[
https://issues.apache.org/jira/browse/HBASE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795483#action_12795483
]
stack commented on HBASE-2079:
------------------------------
Well, thinking on it, my change will not work. It just blocks threads on
hashcode but issue is changes in backing Map while an iteration is going on.
Would need to synchronize all puts to HBC since the Configuration backing
Properties is not accessible.
I'm going to cancel patch and move this out of 0.20.3. Its rare and the
workaround is to set all configuration before starting up threads.
> CME in HBC#hashCode
> -------------------
>
> Key: HBASE-2079
> URL: https://issues.apache.org/jira/browse/HBASE-2079
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Attachments: 2079.patch
>
>
> From hbase-user. I'm putting it into 0.20.3 Shows when multiple concurrent
> threads.
> {code}
> On Wed, Dec 30, 2009 at 5:59 AM, Dmitriy Lyfar <dly...@gmail.com> wrote:
> Exception in thread "Thread-9" java.util.ConcurrentModificationException
> at
> java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:1028)
> at org.apache.hadoop.conf.Configuration.getProps(Configuration.java:979)
> at
> org.apache.hadoop.conf.Configuration.iterator(Configuration.java:1015)
> at
> org.apache.hadoop.hbase.HBaseConfiguration.hashCode(HBaseConfiguration.java:63)
> at java.util.WeakHashMap.get(WeakHashMap.java:348)
> at
> org.apache.hadoop.hbase.client.HConnectionManager.getConnection(HConnectionManager.java:97)
> at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:123)
> at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:105)
> at InserterThread.run(hbase_client.java:53)
> at java.lang.Thread.run(Thread.java:619
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
