[ https://issues.apache.org/jira/browse/CASSANDRA-13496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Jirsa resolved CASSANDRA-13496. ------------------------------------ Resolution: Won't Fix As mentioned, this is unlikely to be fixed anytime soon, as is really a case where a new data model should be considered. Without any further quantification, closing as wont-fix. > table with lots of column ( tens of thousands columns), system is very slow > ---------------------------------------------------------------------------- > > Key: CASSANDRA-13496 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13496 > Project: Cassandra > Issue Type: Bug > Components: CQL > Environment: linux redhat 6.5 cassandra 3.10 using 2i > cpu : 4 core , memory: 16G . 5 servers > using gocql client > Reporter: lizg > Priority: Minor > Labels: usability > Attachments: debug.log, sql.txt > > > In debug.log there are lots of > DEBUG [COMMIT-LOG-ALLOCATOR] 2017-05-04 08:54:35,769 > AbstractCommitLogSegmentManager.java:107 - No segments in reserve; creating a > fresh one > DEBUG [MemtablePostFlush:54] 2017-05-04 08:49:19,699 > AbstractCommitLogSegmentManager.java:329 - Segment > CommitLogSegment(/home/matrix/cassandra/commitlog/CommitLog-6-1493809341337.log) > is no longer active and will be deleted now -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org