[
https://issues.apache.org/jira/browse/HADOOP-18931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775281#comment-17775281
]
Viraj Jasani commented on HADOOP-18931:
---------------------------------------
i thought we were already logging it during the first time init of fs for the
given JVM
{code:java}
try {
SERVICE_FILE_SYSTEMS.put(fs.getScheme(), fs.getClass());
if (LOGGER.isDebugEnabled()) {
LOGGER.debug("{}:// = {} from {}",
fs.getScheme(), fs.getClass(),
ClassUtil.findContainingJar(fs.getClass()));
}
} catch (Exception e) {
LOGGER.warn("Cannot load: {} from {}", fs,
ClassUtil.findContainingJar(fs.getClass()));
LOGGER.info("Full exception loading: {}", fs, e);
}
{code}
maybe you are suggesting that we should log it for every call to
{_}getFileSystemClass(){_}, correct?
> FileSystem.getFileSystemClass() to log at debug the jar the .class came from
> ----------------------------------------------------------------------------
>
> Key: HADOOP-18931
> URL: https://issues.apache.org/jira/browse/HADOOP-18931
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 3.3.6
> Reporter: Steve Loughran
> Priority: Minor
>
> we want to be able to log the jar the filesystem implementation class, so
> that we can identify which version of a module the class came from.
> this is to help track down problems where different machines in the cluster
> or the .tar.gz bundle is out of date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
