[
https://issues.apache.org/jira/browse/CASSANDRA-18022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675786#comment-17675786
]
Jordan West commented on CASSANDRA-18022:
-----------------------------------------
New test runs here:
[j11|https://app.circleci.com/pipelines/github/jrwest/cassandra/142/workflows/99bb5ff6-2704-443b-8c26-396fffa2dd2d]
[j8|https://app.circleci.com/pipelines/github/jrwest/cassandra/142/workflows/88ad9267-90ed-433d-b4f0-347d2687dab6]
Pretty sure those failures were a race condition between the sampler threads
and the test thread. While I don't love the solution I used, adding sleeps, it
does accurately simulate how profileload works in prod (sleeping between
begin/finishSampling calls).
> Extend profileload to track by additional metrics
> -------------------------------------------------
>
> Key: CASSANDRA-18022
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18022
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
> Reporter: Jordan West
> Assignee: Jordan West
> Priority: Normal
>
> Add option to toppartitions to track by:
> * Row Count
> * Tombstone Count
> * SSTable Count
> * Latency
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
