You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "gaojinchao (Created) (JIRA)" <ji...@apache.org> on 2011/10/24 03:30:32 UTC
[jira] [Created] (HBASE-4651) TestHCM case
fails(ConcurrentModificationException might be thrown in
TestHCM.testConnectionUniqueness)
TestHCM case fails(ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness)
-------------------------------------------------------------------------------------------------------
Key: HBASE-4651
URL: https://issues.apache.org/jira/browse/HBASE-4651
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.0
Reporter: gaojinchao
Priority: Minor
Fix For: 0.92.0
looks Ted's mail
ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness.
See
https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
363 Entry<K,V> nextEntry() {
364 if (modCount != expectedModCount)
365 throw new
ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
[image:
JavaDoc] <http://kickjava.com/2487.htm>();
Read more:
http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
HCM uses proper synchronization when accessing HBASE_INSTANCES.
Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
I simplified TestHCM.getValidKeyCount() by returning cache.size() directly where ConcurrentModificationException isn't thrown.
The test passed.
Please comment on proposed simplification.
--
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] [Commented] (HBASE-4651) ConcurrentModificationException
might be thrown in TestHCM.testConnectionUniqueness
Posted by "gaojinchao (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133819#comment-13133819 ]
gaojinchao commented on HBASE-4651:
-----------------------------------
Results :
Tests in error:
testBadOriginalRootLocation(org.apache.hadoop.hbase.catalog.TestCatalogTrackerOnCluster): unknown host: example.org
Tests run: 1043, Failures: 0, Errors: 1, Skipped: 16
TestCatalogTrackerOnCluster failed because it couldn't connect the network. I modified "example.org
" for my local machine name and it passed.
-------------------------------------------------------
T E S T S
-------------------------------------------------------
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.hadoop.hbase.catalog.TestCatalogTrackerOnCluster
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 40.175 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness
> -----------------------------------------------------------------------------------
>
> Key: HBASE-4651
> URL: https://issues.apache.org/jira/browse/HBASE-4651
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: gaojinchao
> Assignee: gaojinchao
> Priority: Minor
> Fix For: 0.92.0
>
>
> See
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
> 363 Entry<K,V> nextEntry() {
> 364 if (modCount != expectedModCount)
> 365 throw new
> ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
> [image:
> JavaDoc] <http://kickjava.com/2487.htm>();
> Read more:
> http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
> HCM uses proper synchronization when accessing HBASE_INSTANCES.
> Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
> However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
> TestHCM.getValidKeyCount() can be removed from the test.
--
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] [Updated] (HBASE-4651) ConcurrentModificationException might
be thrown in TestHCM.testConnectionUniqueness
Posted by "Ted Yu (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-4651:
--------------------------
Description:
See
https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
363 Entry<K,V> nextEntry() {
364 if (modCount != expectedModCount)
365 throw new
ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
[image:
JavaDoc] <http://kickjava.com/2487.htm>();
Read more:
http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
HCM uses proper synchronization when accessing HBASE_INSTANCES.
Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
TestHCM.getValidKeyCount() can be removed from the test.
was:
looks Ted's mail
ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness.
See
https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
363 Entry<K,V> nextEntry() {
364 if (modCount != expectedModCount)
365 throw new
ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
[image:
JavaDoc] <http://kickjava.com/2487.htm>();
Read more:
http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
HCM uses proper synchronization when accessing HBASE_INSTANCES.
Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
I simplified TestHCM.getValidKeyCount() by returning cache.size() directly where ConcurrentModificationException isn't thrown.
The test passed.
Please comment on proposed simplification.
Summary: ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness (was: TestHCM case fails(ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness))
> ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness
> -----------------------------------------------------------------------------------
>
> Key: HBASE-4651
> URL: https://issues.apache.org/jira/browse/HBASE-4651
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: gaojinchao
> Assignee: gaojinchao
> Priority: Minor
> Fix For: 0.92.0
>
>
> See
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
> 363 Entry<K,V> nextEntry() {
> 364 if (modCount != expectedModCount)
> 365 throw new
> ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
> [image:
> JavaDoc] <http://kickjava.com/2487.htm>();
> Read more:
> http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
> HCM uses proper synchronization when accessing HBASE_INSTANCES.
> Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
> However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
> TestHCM.getValidKeyCount() can be removed from the test.
--
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] [Assigned] (HBASE-4651) TestHCM case
fails(ConcurrentModificationException might be thrown in
TestHCM.testConnectionUniqueness)
Posted by "gaojinchao (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
gaojinchao reassigned HBASE-4651:
---------------------------------
Assignee: gaojinchao
> TestHCM case fails(ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness)
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-4651
> URL: https://issues.apache.org/jira/browse/HBASE-4651
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: gaojinchao
> Assignee: gaojinchao
> Priority: Minor
> Fix For: 0.92.0
>
>
> looks Ted's mail
> ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness.
> See
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
> 363 Entry<K,V> nextEntry() {
> 364 if (modCount != expectedModCount)
> 365 throw new
> ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
> [image:
> JavaDoc] <http://kickjava.com/2487.htm>();
> Read more:
> http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
> HCM uses proper synchronization when accessing HBASE_INSTANCES.
> Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
> However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
> I simplified TestHCM.getValidKeyCount() by returning cache.size() directly where ConcurrentModificationException isn't thrown.
> The test passed.
> Please comment on proposed simplification.
--
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] [Commented] (HBASE-4651) ConcurrentModificationException
might be thrown in TestHCM.testConnectionUniqueness
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135121#comment-13135121 ]
Hudson commented on HBASE-4651:
-------------------------------
Integrated in HBase-0.92 #79 (See [https://builds.apache.org/job/HBase-0.92/79/])
HBASE-4651 ConcurrentModificationException might be thrown in
TestHCM.testConnectionUniqueness (Jinchao)
tedyu :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/client/TestHCM.java
> ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness
> -----------------------------------------------------------------------------------
>
> Key: HBASE-4651
> URL: https://issues.apache.org/jira/browse/HBASE-4651
> Project: HBase
> Issue Type: Test
> Affects Versions: 0.92.0
> Reporter: gaojinchao
> Assignee: gaojinchao
> Priority: Minor
> Fix For: 0.92.0
>
> Attachments: HBASE-4651_Trunk.patch
>
>
> See
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
> 363 Entry<K,V> nextEntry() {
> 364 if (modCount != expectedModCount)
> 365 throw new
> ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
> [image:
> JavaDoc] <http://kickjava.com/2487.htm>();
> Read more:
> http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
> HCM uses proper synchronization when accessing HBASE_INSTANCES.
> Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
> However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
> TestHCM.getValidKeyCount() can be removed from the test.
--
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] [Commented] (HBASE-4651) ConcurrentModificationException
might be thrown in TestHCM.testConnectionUniqueness
Posted by "Ted Yu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133823#comment-13133823 ]
Ted Yu commented on HBASE-4651:
-------------------------------
+1 on patch.
> ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness
> -----------------------------------------------------------------------------------
>
> Key: HBASE-4651
> URL: https://issues.apache.org/jira/browse/HBASE-4651
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: gaojinchao
> Assignee: gaojinchao
> Priority: Minor
> Fix For: 0.92.0
>
> Attachments: HBASE-4651_Trunk.patch
>
>
> See
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
> 363 Entry<K,V> nextEntry() {
> 364 if (modCount != expectedModCount)
> 365 throw new
> ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
> [image:
> JavaDoc] <http://kickjava.com/2487.htm>();
> Read more:
> http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
> HCM uses proper synchronization when accessing HBASE_INSTANCES.
> Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
> However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
> TestHCM.getValidKeyCount() can be removed from the test.
--
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] [Updated] (HBASE-4651) ConcurrentModificationException might
be thrown in TestHCM.testConnectionUniqueness
Posted by "Ted Yu (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-4651:
--------------------------
Issue Type: Test (was: Bug)
Integrated to 0.92 and TRUNK.
Thanks for the patch Jinchao.
> ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness
> -----------------------------------------------------------------------------------
>
> Key: HBASE-4651
> URL: https://issues.apache.org/jira/browse/HBASE-4651
> Project: HBase
> Issue Type: Test
> Affects Versions: 0.92.0
> Reporter: gaojinchao
> Assignee: gaojinchao
> Priority: Minor
> Fix For: 0.92.0
>
> Attachments: HBASE-4651_Trunk.patch
>
>
> See
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
> 363 Entry<K,V> nextEntry() {
> 364 if (modCount != expectedModCount)
> 365 throw new
> ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
> [image:
> JavaDoc] <http://kickjava.com/2487.htm>();
> Read more:
> http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
> HCM uses proper synchronization when accessing HBASE_INSTANCES.
> Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
> However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
> TestHCM.getValidKeyCount() can be removed from the test.
--
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] [Commented] (HBASE-4651) ConcurrentModificationException
might be thrown in TestHCM.testConnectionUniqueness
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134420#comment-13134420 ]
Hudson commented on HBASE-4651:
-------------------------------
Integrated in HBase-TRUNK #2363 (See [https://builds.apache.org/job/HBase-TRUNK/2363/])
HBASE-4651 ConcurrentModificationException might be thrown in
TestHCM.testConnectionUniqueness (Jinchao)
tedyu :
Files :
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/client/TestHCM.java
> ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness
> -----------------------------------------------------------------------------------
>
> Key: HBASE-4651
> URL: https://issues.apache.org/jira/browse/HBASE-4651
> Project: HBase
> Issue Type: Test
> Affects Versions: 0.92.0
> Reporter: gaojinchao
> Assignee: gaojinchao
> Priority: Minor
> Fix For: 0.92.0
>
> Attachments: HBASE-4651_Trunk.patch
>
>
> See
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
> 363 Entry<K,V> nextEntry() {
> 364 if (modCount != expectedModCount)
> 365 throw new
> ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
> [image:
> JavaDoc] <http://kickjava.com/2487.htm>();
> Read more:
> http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
> HCM uses proper synchronization when accessing HBASE_INSTANCES.
> Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
> However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
> TestHCM.getValidKeyCount() can be removed from the test.
--
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] [Resolved] (HBASE-4651) ConcurrentModificationException
might be thrown in TestHCM.testConnectionUniqueness
Posted by "Ted Yu (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu resolved HBASE-4651.
---------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
> ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness
> -----------------------------------------------------------------------------------
>
> Key: HBASE-4651
> URL: https://issues.apache.org/jira/browse/HBASE-4651
> Project: HBase
> Issue Type: Test
> Affects Versions: 0.92.0
> Reporter: gaojinchao
> Assignee: gaojinchao
> Priority: Minor
> Fix For: 0.92.0
>
> Attachments: HBASE-4651_Trunk.patch
>
>
> See
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
> 363 Entry<K,V> nextEntry() {
> 364 if (modCount != expectedModCount)
> 365 throw new
> ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
> [image:
> JavaDoc] <http://kickjava.com/2487.htm>();
> Read more:
> http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
> HCM uses proper synchronization when accessing HBASE_INSTANCES.
> Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
> However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
> TestHCM.getValidKeyCount() can be removed from the test.
--
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] [Updated] (HBASE-4651) ConcurrentModificationException might
be thrown in TestHCM.testConnectionUniqueness
Posted by "gaojinchao (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
gaojinchao updated HBASE-4651:
------------------------------
Attachment: HBASE-4651_Trunk.patch
> ConcurrentModificationException might be thrown in TestHCM.testConnectionUniqueness
> -----------------------------------------------------------------------------------
>
> Key: HBASE-4651
> URL: https://issues.apache.org/jira/browse/HBASE-4651
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: gaojinchao
> Assignee: gaojinchao
> Priority: Minor
> Fix For: 0.92.0
>
> Attachments: HBASE-4651_Trunk.patch
>
>
> See
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/2357/testReport/junit/org.apache.hadoop.hbase.client/TestHCM/testConnectionUniqueness
> 363 Entry<K,V> nextEntry() {
> 364 if (modCount != expectedModCount)
> 365 throw new
> ConcurrentModificationException<http://kickjava.com/src/java/util/ConcurrentModificationException.java.htm>
> [image:
> JavaDoc] <http://kickjava.com/2487.htm>();
> Read more:
> http://kickjava.com/src/java/util/LinkedHashMap.java.htm#ixzz1bbCC0gaT
> HCM uses proper synchronization when accessing HBASE_INSTANCES.
> Looking at TestHCM.getValidKeyCount(), it puts values of HBASE_INSTANCES in a Set and returns the size of the Set.
> However, post HBASE-3777, the values (HConnectionImplementation's) in HBASE_INSTANCES would be unique.
> TestHCM.getValidKeyCount() can be removed from the test.
--
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