You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2022/03/29 12:32:00 UTC

[jira] [Created] (HADOOP-18185) tune logging of prefetch problems

Steve Loughran created HADOOP-18185:
---------------------------------------

             Summary: 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


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.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org