[
https://issues.apache.org/jira/browse/HADOOP-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17580717#comment-17580717
]
Steve Loughran commented on HADOOP-18185:
-----------------------------------------
+many of the info log entries should go to debug; error in prefetch go to info
with stack only at debug.
prefetch ioes can be recovered from, so no need to overreact.
> 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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
