bharath v created IMPALA-7670:
---------------------------------
Summary: Drop table with a concurrent refresh throws
ConcurrentModificationException
Key: IMPALA-7670
URL: https://issues.apache.org/jira/browse/IMPALA-7670
Project: IMPALA
Issue Type: Bug
Components: Catalog
Affects Versions: Impala 3.1.0
Reporter: bharath v
* This is a Catalog V2 only bug*.
Saw this in the Catalog server.
{noformat}
I1004 16:38:55.236702 85380 jni-util.cc:308]
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
at java.util.HashMap$ValueIterator.next(HashMap.java:1471)
at
org.apache.impala.catalog.FeFsTable$Utils.getPartitionFromThriftPartitionSpec(FeFsTable.java:407)
at
org.apache.impala.catalog.HdfsTable.getPartitionFromThriftPartitionSpec(HdfsTable.java:694)
at org.apache.impala.catalog.Catalog.getHdfsPartition(Catalog.java:407)
at org.apache.impala.catalog.Catalog.getHdfsPartition(Catalog.java:386)
at
org.apache.impala.service.CatalogOpExecutor.bulkAlterPartitions(CatalogOpExecutor.java:3193)
at
org.apache.impala.service.CatalogOpExecutor.dropTableStats(CatalogOpExecutor.java:1255)
at
org.apache.impala.service.CatalogOpExecutor.dropStats(CatalogOpExecutor.java:1148)
at
org.apache.impala.service.CatalogOpExecutor.execDdlRequest(CatalogOpExecutor.java:301)
at org.apache.impala.service.JniCatalog.execDdl(JniCatalog.java:157)
{noformat}
Still need to dig into it, but seems like something is off with locking
somewhere.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
