-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node.follow_system_log
may not find a really existing log line
#8720
Comments
what do you think, how can we get to a situation we start waiting after the action here ? |
We missed waiting time before recreating iterator. This causes unnecessary high cpu utilization. refs: scylladb#8720
First issue is that it discovered late the start line (it appeared at 03:34:39 and detected at 03:34:49), maybe sct was too busy, or message not flushed to disk. |
maybe we can combine the patterns and wait for both at the same time ? so at least start using both generator at the same time ? |
We missed waiting time before recreating iterator. This causes unnecessary high cpu utilization. refs: scylladb#8720
We are starting generators at the same time - before triggering action. That's why this issue is a mystery for me. |
We missed waiting time before recreating iterator. This causes unnecessary high cpu utilization. refs: scylladb#8720
We missed waiting time before recreating iterator. This causes unnecessary high cpu utilization. refs: scylladb#8720
We missed waiting time before recreating iterator. This causes unnecessary high cpu utilization. refs: scylladb#8720
We missed waiting time before recreating iterator. This causes unnecessary high cpu utilization. refs: scylladb#8720
We missed waiting time before recreating iterator. This causes unnecessary high cpu utilization. refs: #8720
Issue description
Running
disrupt_load_and_stream
nemesis we expect appearance ofstart
andend
log messages for theload and stream
operation.In current case in first 2 used nodes logs the expected log lines were correctly found:
node-5:
node-4:
But in case of the next
node-3
theend
log line was not detected and the 5 minutes timeout error was raised:node-3:
Steps to Reproduce
disrupt_load_and_stream
nemesisExpected behavior: If a log line exists it must be detected
Actual behavior: Existing log line was not detected
Impact
False negative.
How frequently does it reproduce?
Unknown
Installation details
SCT Version:
master
Scylla version (or git commit hash):
master
Logs
f25dd9b8-587a-49cb-bc78-5b8ed3226c68
The text was updated successfully, but these errors were encountered: