[ 
https://issues.apache.org/jira/browse/CASSANDRA-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825741#comment-17825741
 ] 

Stefan Miklosovic commented on CASSANDRA-19447:
-----------------------------------------------

I noticed that repeated tests in above links timeouted.

This build (1) tests 500x 
org.apache.cassandra.distributed.test.ring.BootstrapTest only as my plan is not 
able to run both tests under 1 hour at once.

https://app.circleci.com/pipelines/github/instaclustr/cassandra/3993/workflows/4a509bbf-4682-4e21-8b65-a47be1e20f5f

I will next run multiplexer for 
org.apache.cassandra.distributed.test.hostreplacement.FailedBootstrapTest

[CASSANDRA-19447|https://github.com/instaclustr/cassandra/tree/CASSANDRA-19447]
{noformat}
java17_pre-commit_tests                         
  ✓ j17_build                                        4m 38s
  ✓ j17_cqlsh_dtests_py311                           6m 50s
  ✓ j17_cqlsh_dtests_py311_vnode                     7m 10s
  ✓ j17_cqlsh_dtests_py38                             7m 6s
  ✓ j17_cqlsh_dtests_py38_vnode                      7m 13s
  ✓ j17_cqlshlib_cython_tests                        9m 37s
  ✓ j17_cqlshlib_tests                               6m 56s
  ✓ j17_dtests                                       35m 1s
  ✓ j17_dtests_latest_repeat                         0m 52s
  ✓ j17_dtests_vnode                                 36m 0s
  ✓ j17_jvm_dtests_latest_vnode_repeat               2m 45s
  ✓ j17_jvm_dtests_repeat                           45m 57s
  ✓ j17_unit_tests                                  14m 12s
  ✓ j17_utests_latest                               14m 19s
  ✓ j17_utests_latest_repeat                         0m 35s
  ✓ j17_jvm_dtests_latest_vnode                      23m 3s
  ✕ j17_dtests_latest                               34m 44s
      cdc_test.TestCDC 
test_insertion_and_commitlog_behavior_after_reaching_cdc_total_space   
CASSANDRA-18160
      bootstrap_test.TestBootstrap test_bootstrap_with_reset_bootstrap_state   
??? 
      offline_tools_test.TestOfflineTools test_sstablelevelreset            ???
      offline_tools_test.TestOfflineTools test_sstableofflinerelevel        ???
      topology_test.TestTopology test_resumable_decommission    CASSANDRA-18828 
still happening
  ✕ j17_jvm_dtests                                  25m 47s
      org.apache.cassandra.fuzz.ring.ConsistentBootstrapTest 
coordinatorIsBehindTest   CASSANDRA-19343
  ✕ j17_utests_oa                                   14m 52s
      org.apache.cassandra.net.ConnectionTest testMessageDeliveryOnReconnect  
CASSANDRA-16677
java17_separate_tests                            
java11_pre-commit_tests                         
java11_separate_tests                            
{noformat}



> Register the measurements of the bootstrap as Dropwizard metrics
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-19447
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19447
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability/JMX, Observability/Metrics
>            Reporter: Maxim Muzafarov
>            Assignee: Maxim Muzafarov
>            Priority: Normal
>             Fix For: 5.x
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently, we can view the node's bootstrap state in the following ways:
> - via the nodetool cli tool, e.g. by running the "resume" command;
> - querying the bootstrapped column of the system_veis.local virtual table;
> In addition, we can also expose the status and state of the node's bootstrap 
> via JMX. This is used by third-party tools that rely entirely on the JMX API 
> and don't have access to the CQL interface. The operator will be able to get 
> all the information they need from the dashboards without having to use CLIs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to