activity | timestamp | source | source_elapsed
------------------------------------------------------------------------------------------------------+--------------+---------------+----------------
execute_cql3_query | 06:30:52,479 | 192.168.11.23 | 0
Parsing select adid from userlastadevents where userid = '90000012' and type in (1,2,3) LIMIT 10000; | 06:30:52,479 | 192.168.11.23 | 44
Peparing statement | 06:30:52,479 | 192.168.11.23 | 146
Executing single-partition query on userlastadevents | 06:30:52,480 | 192.168.11.23 | 665
Acquiring sstable references | 06:30:52,480 | 192.168.11.23 | 680
Executing single-partition query on userlastadevents | 06:30:52,480 | 192.168.11.23 | 696
Acquiring sstable references | 06:30:52,480 | 192.168.11.23 | 704
Merging memtable tombstones | 06:30:52,480 | 192.168.11.23 | 706
Merging memtable tombstones | 06:30:52,480 | 192.168.11.23 | 721
Bloom filter allows skipping sstable 37398 | 06:30:52,480 | 192.168.11.23 | 758
Bloom filter allows skipping sstable 37426 | 06:30:52,480 | 192.168.11.23 | 762
Bloom filter allows skipping sstable 35504 | 06:30:52,480 | 192.168.11.23 | 768
Bloom filter allows skipping sstable 36671 | 06:30:52,480 | 192.168.11.23 | 771
Merging data from memtables and 0 sstables | 06:30:52,480 | 192.168.11.23 | 777
Merging data from memtables and 0 sstables | 06:30:52,480 | 192.168.11.23 | 780
Executing single-partition query on userlastadevents | 06:30:52,480 | 192.168.11.23 | 782
Acquiring sstable references | 06:30:52,480 | 192.168.11.23 | 791
Read 0 live and 0 tombstoned cells | 06:30:52,480 | 192.168.11.23 | 797
Read 0 live and 0 tombstoned cells | 06:30:52,480 | 192.168.11.23 | 800
Merging memtable tombstones | 06:30:52,480 | 192.168.11.23 | 815
Bloom filter allows skipping sstable 37432 | 06:30:52,480 | 192.168.11.23 | 857
Bloom filter allows skipping sstable 36918 | 06:30:52,480 | 192.168.11.23 | 866
Merging data from memtables and 0 sstables | 06:30:52,480 | 192.168.11.23 | 874
Read 0 live and 0 tombstoned cells | 06:30:52,480 | 192.168.11.23 | 898
Request complete | 06:30:52,479 | 192.168.11.23 | 990
以上是来自cassandra cqlsh的单个查询的跟踪输出,但我并没有理解一些条目,首先列“source_elapsed”是什么意思,是否意味着执行特定任务所用的时间或累计到此任务的时间。第二个“时间戳记”不会像“请求完整”时间戳那样维护时间戳06:30:52,479,但是“合并数据从memtables和0 sstables”是06:30:52,480这是假设较早发生,但时间戳显示它发生在稍后。什么是cqlsh跟踪条目的含义?
看不惯一些活动,以及,
执行单分区查询 - 并不意味着所有的任务,作为一个整体还是一个起点?它包括的工作是什么?为什么它重复三次?它是否与复制因素有关?
获取sstable引用 - 它是什么意思,它检查所有sstable的bloom过滤器是否包含我们搜索的特定键?然后在“分区索引”的帮助下找到数据文件中的引用。
布隆过滤器允许跳过sstable - 它什么时候发生?它是如何发生的?它寻找sstable引用的时间是相同的。
请求完成 - 这是什么意思?是终点线还是需要花费大量时间的工作?
感谢您的回答,我曾经经历过这些,但无法按照我的预期获得详细信息。 但我给你+1 – Zer001