[
https://issues.apache.org/jira/browse/CASSANDRA-19577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839848#comment-17839848
]
Caleb Rackliffe edited comment on CASSANDRA-19577 at 4/23/24 4:29 PM:
----------------------------------------------------------------------
The [4.1 patch|https://github.com/apache/cassandra/pull/3268] is up.
CI results are clean, modulo a couple environment specific things, OOMs, and
known issues that have nothing to do w/ vtables or {{DebuggableTask}}.
was (Author: maedhroz):
The [4.1 patch|https://github.com/apache/cassandra/pull/3268] is up. CI results
will be posted soon...
> Queries are not visible to the "system_views.queries" virtual table at the
> coordinator level
> --------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19577
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19577
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Virtual Tables
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.1
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There appears to be a hole in the implementation of CASSANDRA-15241 where
> {{DebuggableTasks}} at the coordinator are not preserved through the creation
> of {{FutureTasks}} in {{TaskFactory}}. This means that {{QueriesTable}} can't
> see them when is asks {{SharedExecutorPool}} for running tasks. It should be
> possible to fix this in {{TaskFactory}} by making sure to propagate any
> {{RunnableDebuggableTask}} we encounter. We already do this in
> {{toExecute()}}, but it also needs to happen in the relevant {{toSubmit()}}
> method(s).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
