0

运行 DSE 4.8.10 - 我的集群中有 3 个 DSE 搜索节点，RF=3。我在 system.log 中看到一些消息，如下所示。似乎它们总是在压实之后出现。solr 索引是否有问题，或者至少有这些消息的解释？

INFO [CompactionExecutor:12] 2016-11-14 23:09:31,243 CompactionTask.java:274 - Compacted 4 sstables to [/data/lib/cassandra/data/system/local/system-local-ka-13314,]. 1,564 bytes to 1,378 (~88% of original) in 17ms = 0.077304MB/s. 4 total partitions merged to 1. Partition merge counts were {4:1, } INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,008 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,053 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,144 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,187 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,230 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,270 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,311 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,353 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,395 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,436 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,478 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,519 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,559 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,600 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,640 AbstractSolrSecondaryIndex.java:1689 - Found 200 rows with expired columns. INFO [Solr TTL scheduler-0] 2016-11-14 23:09:36,681 AbstractSolrSecondaryIndex.java:1689 - Found 31 rows with expired columns.

4

1 回答 1

0

我假设您在数据上设置了一些 TTL。

If you want to expire data in a cassandra, you don’t have much choice: you need a periodic task that somehow finds expired data and removes it. With lots of data, keeping this efficient can be a challenge. Cassandra actually includes a great opportunity for that kind of job: compaction. Compaction already goes through your data periodically, throwing away old versions of your data, so it is really easy and cheap to use it for data expiration.

这可能是您仅在压缩后才看到这些消息的原因。

你可以在这里阅读更多： http ://www.datastax.com/dev/blog/whats-new-cassandra-07-expiring-columns

于 2016-11-15T02:07:16.403 回答