From 8f64b46de1c62f327a72900f8dda849f9fe84973 Mon Sep 17 00:00:00 2001 From: Yang Wang Date: Mon, 21 Jul 2025 11:57:45 +1000 Subject: [PATCH] Skip stacktrace in info log for s3 region loading issue The stacktrace is rather excessive given the level of the log message. The information provided in the exception message should be sufficient for taking actions. Also adjust the wording to better match the contribuation guide for logging messages. --- .../org/elasticsearch/repositories/s3/S3RepositoryPlugin.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3RepositoryPlugin.java b/modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3RepositoryPlugin.java index ab836040efa9a..278160fe5aaf6 100644 --- a/modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3RepositoryPlugin.java +++ b/modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3RepositoryPlugin.java @@ -101,7 +101,7 @@ private static Region getDefaultRegion() { try { return DefaultAwsRegionProviderChain.builder().build().getRegion(); } catch (Exception e) { - logger.info("failed to obtain region from default provider chain", e); + logger.info("unable to obtain region from default provider chain: {}", e.getMessage()); return null; } }