cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eduard Tudenhoefner (JIRA)" <>
Subject [jira] [Comment Edited] (CASSANDRA-13533) ColumnIdentifier object size wrong when tables are not flushed
Date Tue, 16 May 2017 16:32:04 GMT


Eduard Tudenhoefner edited comment on CASSANDRA-13533 at 5/16/17 4:32 PM:


was (Author: eduard.tudenhoefner):

> ColumnIdentifier object size wrong when tables are not flushed
> --------------------------------------------------------------
>                 Key: CASSANDRA-13533
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Eduard Tudenhoefner
>            Assignee: Eduard Tudenhoefner
>             Fix For: 3.0.14, 3.11.0, 4.0
> It turns out that the object size of {{ColumnIdentifier}} is wrong when *cassandra.test.flush_local_schema_changes:
false*. This looks like stuff is being wrongly reused when no flush is happening.
> We only noticed this because we were using the prepared stmt cache and noticed that prepared
statements would account for *1-6mb* when *cassandra.test.flush_local_schema_changes: false*.
With *cassandra.test.flush_local_schema_changes: true* (which is the default) those would
be around *5000 bytes*.
> Attached is a test that reproduces the problem and also a fix.
> Also after talking to [~jkni] / [~blerer] we shouldn't probably take {{ColumnDefinition}}
into account when measuring object sizes with {{MemoryMeter}}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message