cqlsh跟踪条目是什么意思? [英] what are cqlsh tracing entries meaning?

查看:62
本文介绍了cqlsh跟踪条目是什么意思?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

 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,但是合并来自内存表和0 sstables的数据"是06:30:52,480,该时间可能早些发生,但时间戳表明它发生得更晚.

Above is the tracing output from cassandra cqlsh for a single query, but I couln't understand some the entries, at first the column "source_elapsed" what does it mean, does it mean time elapsed to execute particular task or cumulative time elapsed up to this task. second "timestamp" doesn't maintain chronology like "Request Complete" timestamp is 06:30:52,479 but "Merging data from memtables and 0 sstables" is 06:30:52,480 which is suppose to happen earlier but timestamp shows it happens later.

也无法理解其中的一些活动,

And couldn't understand some of the activities as well,

  1. 执行单分区查询-是不是整体上意味着所有任务,还是起点?它包括什么工作?为什么重复三遍呢?它是否链接到复制因子.

  1. Executing single-partition query -- doesn't it mean all the task as a whole or is it a starting point? what are the job it includes? And why is it repeating three times? is it link to replication factor.

获取sstable引用-这是什么意思,它是否检查所有sstable的Bloom筛选器是否包含我们要搜索的特定键?然后借助分区索引"在数据文件中找到引用.

Acquiring sstable references -- What does it mean, does it checks all the sstable's bloom filters whether that contains a particular key we search for? An then find the reference in data file with the help of "Partition Index".

Bloom过滤器允许跳过sstable-它何时发生?它是如何发生的?查找稳定引用需要花费相同的时间.

Bloom filter allows skipping sstable -- when does it happen? How does it happen? it is taking same amount of time of finding sstable references.

请求完成-这是什么意思?是终点线还是需要大量时间的工作?

Request complete -- what does it mean? is it the finishing line or it is some job which takes most amount of time?

推荐答案

您是否看到了 Cassandra中的请求跟踪链接说明了不同的跟踪情况?

Did you see the request tracing in Cassandra link that explains different tracing scenarios?

  1. source_elapsed :是特定节点上的累积执行时间(如果您选中上面的链接,它将更加清楚)
  2. 执行单分区查询 :(似乎代表着)开始时间
  3. 请求已完成:此请求已完成所有工作
  1. source_elapsed: is the cumulative execution time on a specific node (if you check the above link it will be clearer)
  2. Executing single-partition query: (seems to represent) the start time
  3. Request complete: all work has been done for this request

对于其他情况,最好阅读阅读Cassandra文档,因为它比我在这里总结的详细得多.

For the rest you'd be better off reading the Reads in Cassandra docs as that would be much more detailed than I could summarize it here.

这篇关于cqlsh跟踪条目是什么意思?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆