Uh oh!
There was an error while loading. Please reload this page.
TEZ-4357: Report url to logs in case of fetcher connection failure - #169
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
| "Fetch Failure while connecting from %s to: %s:%d, attempt: %sInforming ShuffleManager: ", | ||
| localHostname, host, port, firstAttempt), e); | ||
| "Fetch Failure while connecting from %s to: %s:%d, attempt: %s, url: %s Informing ShuffleManager", | ||
| localHostname, host, port, firstAttempt, baseURI.toString()), e); |
There was a problem hiding this comment.
Do we need to call toString() here, %s can take any type & the output is always string right? BTW why aren't we using Logger format here like {} instead of String.format?
There was a problem hiding this comment.
using {} format would make sense but we cannot mix the format arguments and exception in any of the LOG.warn methods
toString can be removed yeah
UPDATE: oh wait, just checked, last argument of vararg is a throwable candidate, so we can use formats here|
public void warn(String format, Object... argArray) {
if (logger.isEnabledFor(Level.WARN)) {
FormattingTuple ft = MessageFormatter.arrayFormat(format, argArray);
logger.log(FQCN, Level.WARN, ft.getMessage(), ft.getThrowable());
}
}
8fd6d0f to
36559dfCompareabstractdog
commented
Nov 17, 2022
addressed comments + added a "FETCH_FAILURE" log prefix which is common for Fetcher and FetcherOrderedGrouped, so makes it easier to scan through app logs for fetch failures |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
tez-yetus
commented
Jan 25, 2024
💔 -1 overall
This message was automatically generated. |
No description provided.