Similar to issue #54. There is another case within ColumnFamilyIterator::next() where it's possible to recurse too deep when a column family contains too many sequential tombstones. In this case if there are 100 bufferload's worth of tombstones (or 1,000 tombstones) in a row then next() will recurse too far looking for a non-zero column row. I have a fix for which I'll create a pull request.
Similar to issue #54. There is another case within ColumnFamilyIterator::next() where it's possible to recurse too deep when a column family contains too many sequential tombstones. In this case if there are 100 bufferload's worth of tombstones (or 1,000 tombstones) in a row then next() will recurse too far looking for a non-zero column row. I have a fix for which I'll create a pull request.