-
Notifications
You must be signed in to change notification settings - Fork 143
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
Materialized views: View local update description #2403
Comments
The relevant Scylla code is https://github.com/scylladb/scylladb/blob/c17d353718464bae230331d7e77d4901281fc017/replica/database.cc#L618 I would like someone from MV to have a look and give their input |
@mykaul can we have someone from MV comment on the issue? |
I suggest changing the panels' names and descriptions in the following way:
@vreniers does this sound good? |
A small change perhaps to "local view updates" description. What do you think @piodul? Otherwise, looks good. |
Installation details
Panel Name: View Local Update
Dashboard Name: Detailed
Scylla-Monitoring Version: 4.7.2
Scylla-Version: 2024.1.4
While investigating a certain dashboard, I was under the impression that "view local update" actually reflected all updates that are happening on a given replica for that materialized view. Its description mentions for example:
View local update - description: "Number of view update locally"
However, it seems this is not true, and that this is a coordinator-side metric. It does not encompass all updates that are happening locally on that replica with regards to a materialized view.
For example, one could assume that all remote view updates that are being sent out (e.g. 200 remote view updates), would show many local view updates (across other shards, of which the sum could amount to 200) - but that is not what this graph shows. It only seems to show the portion of the updates that remain on the coordinator - and that update a view locally there.
I suggest to perhaps mention or clarify in the description that this is a coordinator-side metric.
The text was updated successfully, but these errors were encountered: