Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New LWT metrics for the dasboard #936

Closed
tzach opened this issue May 17, 2020 · 6 comments · Fixed by #1190
Closed

New LWT metrics for the dasboard #936

tzach opened this issue May 17, 2020 · 6 comments · Fixed by #1190

Comments

@tzach
Copy link
Contributor

tzach commented May 17, 2020

  • cas_total_operations - number of total paxos operations executed (reads and writes
  • cas_foreground - how many paxos operations that did not yet produce a result are running
  • cas_background -how many paxos operations are still running after a result was alredy returned
    scylladb/scylladb@d555fb6
@amnonh amnonh added this to the monitoring 3.5 milestone May 18, 2020
@amnonh
Copy link
Collaborator

amnonh commented Jun 28, 2020

@tzach @kostja to which scylla OS/enterprise this applies to?

@amnonh amnonh modified the milestones: monitoring 3.5, monitoring 3.6 Jun 28, 2020
@amnonh
Copy link
Collaborator

amnonh commented Jun 28, 2020

It's not part of 4.1

@amnonh
Copy link
Collaborator

amnonh commented Sep 22, 2020

@tzach @kostja what scylla version this applies to?

@amnonh
Copy link
Collaborator

amnonh commented Sep 22, 2020

Is cas_total_operations relevant? we show read/write

@kostja
Copy link

kostja commented Sep 22, 2020

@tzach @kostja what scylla version this applies to?

4.2+

@kostja
Copy link

kostja commented Sep 22, 2020

Is cas_total_operations relevant? we show read/write

It's a different metric, a single write could have multiple cas operations, it's the total sum for cas_background/foreground metrics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants