Re: MemtableThroughput test in ColumnFamily.apply

wrote: > Makes sense to me, although I don't see it making a material > difference when there are 1000 mutations in a memtable vs 1001. > > On Sat, Feb 25, 2012 at 11:23 AM, Thomas Richter wrote: >> Hi, >> >> while hunting down some memory consumption

MemtableThroughput test in ColumnFamily.apply

Hi, while hunting down some memory consumption issues in 0.7.10 I realized that MemtableThroughput condition is tested before writing the new data. As this causes memtables to grow larger than expected I changed Memtable apply(DecoratedKey key, ColumnFamily columnFamily) { long start

Node OOM, Slice query - missing data?

Hi there, We run a 3 node cluster with 0.7.8 with replication factor 3 for all key spaces. We store external->internal key mappings in a column family with one row for each customer. The largest row contains abount 200k columns. If we import external data we load the whole row and map externa

Re: [Solved] column index offset miscalculation

probably require that you create an account. > > -- > Sylvain > > On Thu, Oct 13, 2011 at 3:20 PM, Thomas Richter wrote: >> Hi Aaron, >> >> the fix does the trick. I wonder why nobody else ran into this before... >> I checked org/apache/cassandra/db/ColumnIndex

[Solved] column index offset miscalculation (was: Existing column(s) not readable)

10/13/2011 10:52 AM, Thomas Richter wrote: > Hi Aaron, > > I guess i found it :-). > > I added logging for the used IndexInfo to > SSTableNamesIterator.readIndexedColumns and got negative index postions > for the missing columns. This is the reason why the columns are not >

Re: Existing column(s) not readable

h other instances. > > A > > - > Aaron Morton > Freelance Cassandra Developer > @aaronmorton > http://www.thelastpickle.com > > - > Aaron Morton > Freelance Cassandra Developer > @aaronmorton > http://www.thelastpickle.com > >

Re: Existing column(s) not readable

t; possible to read columns from a row with a tombstone. > > Can you read the column using a slice range rather than specifying it's name > ? > > Aaron > > - > Aaron Morton > Freelance Cassandra Developer > @aaronmorton > http://www.thel

Re: Existing column(s) not readable

m (all of the) sstables. > If you do not get a column returned I would say there is a tombstone in > place. It's either a row level or a column level one. > > Hope that helps. > > - > Aaron Morton > Freelance Cassandra Developer > @aaronmorton

Re: Existing column(s) not readable

> > What sort of read ? > What client ? > What is in the logging on client and server side ? > > > Try turning the logging up to DEBUG on the server to watch what happens. > > Cheers > > - > Aaron Morton > Freelance Cassandra Develop

Re: Existing column(s) not readable

a Developer > @aaronmorton > http://www.thelastpickle.com > > On 10/10/2011, at 7:42 AM, Thomas Richter wrote: > >> Hi, >> >> here is some further information. Compaction did not help, but data is >> still there when I dump the row with sstable2json. >> &g

Re: Existing column(s) not readable

Hi, here is some further information. Compaction did not help, but data is still there when I dump the row with sstable2json. Best, Thomas On 10/08/2011 11:30 PM, Thomas Richter wrote: > Hi, > > we are running a 3 node cassandra (0.7.6-2) cluster and some of our > column fami

Existing column(s) not readable

Hi, we are running a 3 node cassandra (0.7.6-2) cluster and some of our column families contain quite large rows (400k+ columns, 4-6GB row size). Replicaton factor is 3 for all keyspaces. The cluster is running fine for several months now and we never experienced any serious trouble. Some days ag