[ https://issues.apache.org/jira/browse/CASSANDRA-19289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811851#comment-17811851 ]
Brandon Williams commented on CASSANDRA-19289: ---------------------------------------------- bq. materialized_views_test.TestMaterializedViews test_complex_mv_select_statements This looks like it exposed a bug and we should file a ticket for it, but the rest looks good to me. bq. I did this small change I'm good with that, but...we should probably have CI check it. > Expose core_pool_size, max_pool_size and max_tasks_queued in nodetool tpstats > / system_views.thread_pools > --------------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-19289 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19289 > Project: Cassandra > Issue Type: Improvement > Components: Feature/Virtual Tables, Legacy/Core, Tool/nodetool > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Normal > Fix For: 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > It would be nice to expose this information so it is visible from cql(sh) / > nodetool tpstats. I briefly checked the complexity of this and it should be > quite easy, just add few columns in both and put the sizes to metrics so we > can read that. > Without this, I think the only way to know the sizes is to read it from JMX. > I just prefer some more handy and faster way to check the sizes so I can > adjust them accordingly when necessary. -- 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