[
https://issues.apache.org/jira/browse/CASSANDRA-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477176#comment-13477176
]
Chris Herron commented on CASSANDRA-4571:
-----------------------------------------
Yes, seeing the key equality AssertionErrors from two SSTable iterators:
SSTableSliceIterator:60 and SSTableNamesIterator:72.
Also seeing same EOF error reported by [~tjake] in CASSANDRA-4687:
{code}
java.io.IOError: java.io.EOFException: unable to seek to position 61291844 in
/redacted/cassandra/data/test1/redacted/test1-redacted-hf-1-Data.db (59874704
bytes) in read-only mode
at
org.apache.cassandra.io.util.CompressedSegmentedFile.getSegment(CompressedSegmentedFile.java:69)
at
org.apache.cassandra.io.sstable.SSTableReader.getFileDataInput(SSTableReader.java:898)
at
org.apache.cassandra.db.columniterator.SSTableSliceIterator.<init>(SSTableSliceIterator.java:50)
at
org.apache.cassandra.db.filter.SliceQueryFilter.getSSTableColumnIterator(SliceQueryFilter.java:67)
at
org.apache.cassandra.db.filter.QueryFilter.getSSTableColumnIterator(QueryFilter.java:79)
at
org.apache.cassandra.db.CollationController.collectAllData(CollationController.java:256)
at
org.apache.cassandra.db.CollationController.getTopLevelColumns(CollationController.java:64)
at
org.apache.cassandra.db.ColumnFamilyStore.getTopLevelColumns(ColumnFamilyStore.java:1345)
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1207)
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1142)
at org.apache.cassandra.db.Table.getRow(Table.java:378)
at
org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:69)
at
org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:51)
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:59)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.EOFException: unable to seek to position 61291844 in
/redacted/cassandra/data/test1/redacted/test1-redacted-hf-1-Data.db (59874704
bytes) in read-only mode
at
org.apache.cassandra.io.util.RandomAccessReader.seek(RandomAccessReader.java:253)
at
org.apache.cassandra.io.util.CompressedSegmentedFile.getSegment(CompressedSegmentedFile.java:64)
... 16 more
{code}
> Strange permament socket descriptors increasing leads to "Too many open files"
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-4571
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4571
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.1
> Environment: CentOS 5.8 Linux 2.6.18-308.13.1.el5 #1 SMP Tue Aug 21
> 17:10:18 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux.
> java version "1.6.0_33"
> Java(TM) SE Runtime Environment (build 1.6.0_33-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)
> Reporter: Serg Shnerson
> Assignee: Jonathan Ellis
> Priority: Critical
> Fix For: 1.1.5
>
> Attachments: 4571.txt
>
>
> On the two-node cluster there was found strange socket descriptors
> increasing. lsof -n | grep java shows many rows like"
> java 8380 cassandra 113r unix 0xffff8101a374a080
> 938348482 socket
> java 8380 cassandra 114r unix 0xffff8101a374a080
> 938348482 socket
> java 8380 cassandra 115r unix 0xffff8101a374a080
> 938348482 socket
> java 8380 cassandra 116r unix 0xffff8101a374a080
> 938348482 socket
> java 8380 cassandra 117r unix 0xffff8101a374a080
> 938348482 socket
> java 8380 cassandra 118r unix 0xffff8101a374a080
> 938348482 socket
> java 8380 cassandra 119r unix 0xffff8101a374a080
> 938348482 socket
> java 8380 cassandra 120r unix 0xffff8101a374a080
> 938348482 socket
> " And number of this rows constantly increasing. After about 24 hours this
> situation leads to error.
> We use PHPCassa client. Load is not so high (aroud ~50kb/s on write).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
