s3 subsystem not printing error messages by default

XMLWordPrintableJSON

    • StorEng - Refinement Pipeline
    • None

      Looking at WT-10752, we see a failure from what we presume is an S3 network error, but there is no output from the s3 module.  I notice that the s3 logging code in s3_log_system.cpp uses awsLogLevel to control whether logging takes place, but I don't see that initialized, except when it is explicitly configured via verbose=(tiered). In particular, it looks like calls to s3->log->LogErrorMessage are lost unless verbose is set in the wiredtiger_open connection string.  It seems like we should _always receive those messages?

      We should see if gcp and azure have similar issues.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Donald Anderson
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: