[
https://issues.apache.org/jira/browse/HADOOP-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17632254#comment-17632254
]
Daniel Carl Jones commented on HADOOP-18185:
--------------------------------------------
Looking at HADOOP-18351 with [~sauraank], some of the log entries have been
moved from info to debug where appropriate in
[https://github.com/apache/hadoop/commit/36bbde2fda7a21db5|https://github.com/apache/hadoop/commit/36bbde2fda7a21db5bf604c7c661d8cbe8b5326b]
Whoever picks this up - may be worth checking there's no other INFO/WARN/ERROR
that would be better as DEBUG.
> tune logging of prefetch problems
> ---------------------------------
>
> Key: HADOOP-18185
> URL: https://issues.apache.org/jira/browse/HADOOP-18185
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Priority: Major
>
> we need to think what we want to do here.
> * we would want errors to be counted and included in stream iostats
> * but we've seen abfs apps flooded with stack traces when a transient network
> error breaks every prefetch.
> * logging through LogExactlyOnce would highlight a problem, but on a long
> lived process, not show enough, unless the cache manager had a per instance
> value.
> # PrefetchTask needs to be non static and update the CachingBlockManager when
> there is a problem; it can LogExactlyOnce
> # stream statistics need to include cache values (hits, misses, prefech
> failures, how long futures were queued before execution...)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
