You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Ayush Saxena (Jira)" <ji...@apache.org> on 2020/03/15 11:27:00 UTC
[jira] [Updated] (HDFS-15197) [SBN read] Change
ObserverRetryOnActiveException log to debug
[ https://issues.apache.org/jira/browse/HDFS-15197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ayush Saxena updated HDFS-15197:
--------------------------------
Fix Version/s: 2.10.1
3.2.2
3.1.4
3.3.0
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk, branch-3.2,3.1,2.10
Thanx [~vagarychen] for the contribution and [~csun] for the review!!!
> [SBN read] Change ObserverRetryOnActiveException log to debug
> -------------------------------------------------------------
>
> Key: HDFS-15197
> URL: https://issues.apache.org/jira/browse/HDFS-15197
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Reporter: Chen Liang
> Assignee: Chen Liang
> Priority: Minor
> Fix For: 3.3.0, 3.1.4, 3.2.2, 2.10.1
>
> Attachments: HDFS-15197.001.patch
>
>
> Currently in ObserverReadProxyProvider, when a ObserverRetryOnActiveException happens, ObserverReadProxyProvider logs a message at INFO level. This can be a large volume of logs in some scenarios. For example, when some job tries to access lots of files that haven't been accessed for a long time, all these accesses may trigger atime updates, which led to ObserverRetryOnActiveException. We should change this log to DEBUG.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org