Skip to content
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

scylla_forward_service_requests_dispatched_to_other_nodes renamed to scylla_mapreduce_service_requests_dispatched_to_other_nodes #8184

Closed
temichus opened this issue Jul 29, 2024 · 11 comments · Fixed by #8185
Assignees

Comments

@temichus
Copy link
Contributor

Issue description

Fullscan failed with 'forward_service_requests_dispatched_to_other_nodes' was not triggered
due to
scylla_forward_service_requests_dispatched_to_other_nodes renamed to scylla_mapreduce_service_requests_dispatched_to_other_nodes

@roydahan
Copy link
Contributor

roydahan commented Nov 19, 2024

I see these errors now in 2024.2.0 runs (https://argus.scylladb.com/tests/scylla-cluster-tests/cdf5c417-feda-44a4-bb08-46f5de97f29f), but the blamed commit of scylla scylladb/scylladb@3fc4e23 isn't part of this branch AFAICT.

@roydahan
Copy link
Contributor

message=FullScanAggregatesOperation operation failed: Fullscan failed - 'forward_service_requests_dispatched_to_other_nodes' was not triggered

@roydahan roydahan reopened this Nov 19, 2024
@roydahan
Copy link
Contributor

I see that these happened during Decommission nemesis.
It could be related.

@roydahan
Copy link
Contributor

I see it also in this run: https://argus.scylladb.com/tests/scylla-cluster-tests/b9dd8869-3644-49b4-bc4e-478f7282298a.
Here it happened right after a decommission nemesis ended (FullScan started before).

@soyacz
Copy link
Contributor

soyacz commented Nov 19, 2024

we didn't backport it to 2024.2 - which branched a week before this PR. Backporting.

@soyacz
Copy link
Contributor

soyacz commented Nov 19, 2024

backported, closing.

@soyacz soyacz closed this as completed Nov 19, 2024
@roydahan
Copy link
Contributor

@soyacz
Did you find the renaming commit as part of 2024.2?

Why would we need to backport this one if https://github.com/scylladb/scylla-enterprise/commit/3fc4e23a36aad7a418805797b08370a3f3ddae2b is not part of 2024.2 ?

@soyacz
Copy link
Contributor

soyacz commented Nov 19, 2024

@soyacz Did you find the renaming commit as part of 2024.2?

Why would we need to backport this one if scylladb/scylla-enterprise@3fc4e23 is not part of 2024.2 ?

Ugh, I didn't check that and indeed, it's not part of 2024.2. So in that case, why it's an SCT issue and not the scylla-enterprise one?

@roydahan
Copy link
Contributor

I wasn't sure yet when starting to comment on the issue.

@mykaul
Copy link
Contributor

mykaul commented Dec 26, 2024

I see it also in this run: https://argus.scylladb.com/tests/scylla-cluster-tests/b9dd8869-3644-49b4-bc4e-478f7282298a. Here it happened right after a decommission nemesis ended (FullScan started before).

@roydahan - this is (not surprising) also failing on 2024.2.x - do we have a separate bug for it? I could not find one.

@roydahan
Copy link
Contributor

It's not the cause of this issue.
There is an attempt to fix/workaround this issue in this PR:

#9370

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants