cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-8189) tombstone WARN in log file when creating a table with many columns
Date Tue, 04 Nov 2014 22:55:34 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko resolved CASSANDRA-8189.
------------------------------------------
    Resolution: Duplicate

> tombstone WARN in log file when creating a table with many columns
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-8189
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8189
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Oded Peer
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>         Attachments: LargeTableTest.java
>
>
> I created a table with 500 columns, creating the table resulted in a warning in the log
file.
> bq. WARN  10:13:17 Read 2504 live and 1003 tombstoned cells in system.schema_columns
(see tombstone_warn_threshold). 2147483647 columns was requested, slices=[table_0-table_0:!],
delInfo={deletedAt=-9223372036854775808, localDeletion=2147483647}
> See the attached unit test.
> I analyzed the table to understand what are the tombstone columns and it appears that
Cassandra creates deleted columns for "index_type" and "index_name" if they are not present
for a column.
> "index_type" get the String value "null" if it is not present.
> A side effect is that these deleted columns are not removed. Since system.schema_columns
rarely changes compaction never happens for this table and the sstable will retain the deleted
columns.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message