[ https://issues.apache.org/jira/browse/CASSANDRA-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Brosius updated CASSANDRA-4231: ------------------------------------ Comment: was deleted (was: it would seem the endpoint list is changing out from under the RangeClient as the list is referenced shared with the ringCache. ) > ConcurrentModificationException while writing mutations with > ColumnFamilyRecordWrite > ------------------------------------------------------------------------------------ > > Key: CASSANDRA-4231 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4231 > Project: Cassandra > Issue Type: Bug > Components: Hadoop > Affects Versions: 1.0.10 > Environment: Debian Squeeze, one local cassandra node > Reporter: bert Passek > > Hello, > we are using mapreduce jobs for writing data into cassandra. Sometimes the > job fails because of a concurrent modification exception. > java.io.IOException: java.util.ConcurrentModificationException > at > org.apache.cassandra.hadoop.ColumnFamilyRecordWriter$RangeClient.run(ColumnFamilyRecordWriter.java:307) > Caused by: java.util.ConcurrentModificationException > at > java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) > at java.util.AbstractList$Itr.next(AbstractList.java:343) > at org.apache.cassandra.thrift.SuperColumn.write(SuperColumn.java:440) > at > org.apache.cassandra.thrift.ColumnOrSuperColumn.write(ColumnOrSuperColumn.java:561) > at org.apache.cassandra.thrift.Mutation.write(Mutation.java:384) > at > org.apache.cassandra.thrift.Cassandra$batch_mutate_args.write(Cassandra.java:19021) > at > org.apache.cassandra.thrift.Cassandra$Client.send_batch_mutate(Cassandra.java:1018) > at > org.apache.cassandra.thrift.Cassandra$Client.batch_mutate(Cassandra.java:1008) > at > org.apache.cassandra.hadoop.ColumnFamilyRecordWriter$RangeClient.run(ColumnFamilyRecordWriter.java:299) > We were using Cassandra 1.0.8 for quite a long time without such problems. > Regards Bert Passek -- 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