[
https://issues.apache.org/jira/browse/CASSANDRA-19289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811757#comment-17811757
]
Stefan Miklosovic commented on CASSANDRA-19289:
-----------------------------------------------
*CASSANDRA-19289*
{noformat}
java17_pre-commit_tests
j17_jvm_dtests
org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest
testOptionalMtlsModeDoNotAllowNonSSLConnections (1)
org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest
optionalTlsConnectionAllowedToRegularPortTest (2)
org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest
testEndpointVerificationEnabledIpNotInSAN (3)
j17_jvm_dtests_vnode
org.apache.cassandra.distributed.test.jmx.JMXFeatureTest
testOneNetworkInterfaceProvisioning (4)
java11_pre-commit_tests
j11_simulator_dtests
org.apache.cassandra.simulator.test.HarrySimulatorTest test (5)
j11_utests_system_keyspace_directory
org.apache.cassandra.cql3.validation.operations.AlterTest
testAlterStatementWithAdd (6)
j17_dtests_vnode
materialized_views_test.TestMaterializedViews
test_complex_mv_select_statements (7)
j17_jvm_dtests
org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest
testOptionalMtlsModeDoNotAllowNonSSLConnections (8)
j17_jvm_dtests_vnode
org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest
testOptionalMtlsModeDoNotAllowNonSSLConnections (9)
junit.framework.TestSuite
org.apache.cassandra.fuzz.harry.integration.model.InJVMTokenAwareExecutorTest
(10)
{noformat}
(1-3), (8), (9) - CASSANDRA-19281 (does not fail locally)
(4) CASSANDRA-19261
(5) CASSANDRA-19279
(6) in CASSANDRA-19118 Andres said it appeared in CASSANDRA-19245, I rerun the
test in java17_separate_tests/j17_utests_system_keyspace_directory and it passed
(7) I rerun the test in java17_separate_tests/j17_dtest_vnode and they all
passed
(10) timeout, java17_separate_tests/j17_jvm_dtests_vnode passed
[java17_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3811/workflows/aec53330-5c7f-4355-9391-b5a0ce545b54]
[java17_separate_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3811/workflows/ca10e9b4-e833-40f8-8bda-c07f6dae359d]
[java11_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3811/workflows/0e802f47-b17a-427f-8fac-e179d65bb974]
[java11_separate_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3811/workflows/d2f2b42c-e5d1-4266-888b-9201f895f100]
[~brandon.williams] looking good?
> 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
