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

Aleksandr Sorokoumov commented on CASSANDRA-14795:
--------------------------------------------------

I have a suspicion that the test times out because the entire suite takes too 
long to run for the given timeout. We observe it as 
{{HintsServiceTest.testListPendingHints}} failure because it is the last test 
case in the suite.

For test report and logs see e.g. 
https://nightlies.apache.org/cassandra/devbranch/Cassandra-devbranch/1187/

{{test.timeout}} is set to 240 seconds. On successful runs the suite takes a 
bit longer than 200 seconds to finish, each case taking between 30 and 60 
seconds. As a speculation, a small hiccup or a slight deviation in test time 
might lead to a timeout. I'd like to verify this idea by increasing 
{{test.timeout}} to 360 seconds and re-running the CI. If this theory is 
correct, {{HintsServiceTest}} should succeed and overall test duration might 
exceed 240 seconds on 1 or more attempts.

[~azotcsit], [~e.dimitrova] Can I kindly ask you to re-run 
https://ci-cassandra.apache.org/job/Cassandra-devbranch/1187/?



> Expose information about stored hints via JMX
> ---------------------------------------------
>
>                 Key: CASSANDRA-14795
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14795
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Legacy/Observability
>            Reporter: Aleksandr Sorokoumov
>            Assignee: Aleksandr Sorokoumov
>            Priority: Low
>             Fix For: 4.x
>
>          Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> Currently there is no way to determine what kind of hints a node has, apart 
> from looking at the filenames (thus host-ids) on disk. Having a way to access 
> this information would help with debugging hint creation/replay scenarios.
> In addition to the JMX method, there is a new nodetool command:
> {noformat}$ bin/nodetool -h 127.0.0.1 -p 7100 listendpointspendinghints
> Host ID Address Rack DC Status Total files Newest Oldest
> 5762b140-3fdf-4057-9ca7-05c070ccc9c3 127.0.0.2 rack1 datacenter1 DOWN 2 
> 2018-09-18 14:05:18,835 2018-09-18 14:05:08,811
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to