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

[v24.2.x] [CORE-6992] cloud_storage_clients/abs_client: use item filter in list_objects #24454

Merged

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #24439

This seems like an oversight. Noticed in an ABS run of a test:

```
INFO  2024-11-12 02:16:37,966 [shard 1:main] cloud_storage - topic_manifest_downloader.cc:102 - Labeled topic manifest download resulted in 2 matching manifests with prefix '', printing first 2
INFO  2024-11-12 02:16:37,966 [shard 1:main] cloud_storage - topic_manifest_downloader.cc:112 - Match for hint '': meta/kafka/topic-a/83123841-40c1-47e4-92ed-5ac8d1f536c7/8/topic_manifest.bin
INFO  2024-11-12 02:16:37,966 [shard 1:main] cloud_storage - topic_manifest_downloader.cc:112 - Match for hint '': meta/kafka/topic-a/eb0359d1-a0fb-45aa-8995-d938a34caeef/8_lifecycle.bin
WARN  2024-11-12 02:16:37,966 [shard 1:main] kafka - create_topics.cc:185 - Failed to create topic(s) {{kafka/topic-a}} error_code observed: cluster::errc::topic_operation_error
```

In this snippet, the list results contain a lifecycle marker, despite
the filter passed in during manifest download being
ends_with("topic_manifest.bin").

Auditing the codebase a bit, there don't appear to be any other usages
of list_objects() with a filter.

(cherry picked from commit 688480d)
Testing with ABS would have caught a bug in the ABS client during topic
recovery when there are multiple objects within a topic's manifest path
prefix (e.g. from different clusters).

(cherry picked from commit f92108b)
@vbotbuildovich vbotbuildovich added this to the v24.2.x-next milestone Dec 5, 2024
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Dec 5, 2024
@andrwng andrwng merged commit bfe38e4 into redpanda-data:v24.2.x Dec 5, 2024
18 checks passed
@aanthony-rp aanthony-rp modified the milestones: v24.2.x-next, 24.2.14 Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/redpanda kind/backport PRs targeting a stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants