Skip to content

[chore](be) TEST ONLY: add S3 read diagnostics#63107

Draft
Yukang-Lian wants to merge 1 commit intoapache:masterfrom
Yukang-Lian:codex/s3-flush-diagnostic-logs
Draft

[chore](be) TEST ONLY: add S3 read diagnostics#63107
Yukang-Lian wants to merge 1 commit intoapache:masterfrom
Yukang-Lian:codex/s3-flush-diagnostic-logs

Conversation

@Yukang-Lian
Copy link
Copy Markdown
Collaborator

@Yukang-Lian Yukang-Lian commented May 9, 2026

What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: Add diagnostic logs and test-only config changes to capture S3 read context when GetObject fails or returns an unexpected length, helping debug AWS SDK response stream flush failures. This PR sets aws_log_level to Trace for test builds.

Release note

None

Check List (For Author)

  • Test: Manual test
    • Ran git diff --check -- conf/be.conf be/src/io/fs/s3_file_reader.cpp be/src/io/fs/s3_obj_storage_client.cpp.
    • Attempted ./build.sh --be -j8, but it failed before compiling the touched files because /mnt/disk2/lianyukang/doris/thirdparty/installed/lib64/libaws-cpp-sdk-kinesis.a is missing.
  • Behavior changed: Yes. Test-only PR changes default aws_log_level in conf/be.conf from Error to Trace to collect AWS SDK logs.
  • Does this need documentation: No

@hello-stephen
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@Yukang-Lian Yukang-Lian force-pushed the codex/s3-flush-diagnostic-logs branch from 3e95e3d to b7612a5 Compare May 9, 2026 09:52
@Yukang-Lian Yukang-Lian changed the title [chore](be) Add S3 read diagnostics [chore](be) TEST ONLY: add S3 read diagnostics May 9, 2026
### What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: Add diagnostic logs and test-only config changes to capture S3 read context when GetObject fails or returns an unexpected length, helping debug AWS SDK response stream flush failures. This PR sets aws_log_level to Trace for test builds.

### Release note

None

### Check List (For Author)

- Test: Manual test
    - Ran `git diff --check -- conf/be.conf be/src/io/fs/s3_file_reader.cpp be/src/io/fs/s3_obj_storage_client.cpp`.
    - Attempted `./build.sh --be -j8`, but it failed before compiling the touched files because `/mnt/disk2/lianyukang/doris/thirdparty/installed/lib64/libaws-cpp-sdk-kinesis.a` is missing.
- Behavior changed: Yes. Test-only PR changes default `aws_log_level` in `conf/be.conf` from Error to Trace to collect AWS SDK logs.
- Does this need documentation: No
@Yukang-Lian Yukang-Lian force-pushed the codex/s3-flush-diagnostic-logs branch from b7612a5 to 5cb9e82 Compare May 9, 2026 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants