[
https://issues.apache.org/jira/browse/HDFS-14878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941758#comment-16941758
]
Surendra Singh Lilhore commented on HDFS-14878:
-----------------------------------------------
Thanks [~hemanthboyina] for patch.
I also feel it should be warn because user will get to know something is slow
like network/process.
In normal cluster this log will not come because 30s is enough to give the ack.
User can change the threshold by configuring
{{dfs.client.slow.io.warning.threshold.ms.}}
{quote}The existing log level may not be ideal. This is directly visible to
users and unless something actually failed, it is better to log at {{INFO}}
{quote}
[~kihwal], can you recheck your comment once which is given in HDFS-10303 ?
> DataStreamer's ResponseProceesor#run() should log with Warn loglevel
> --------------------------------------------------------------------
>
> Key: HDFS-14878
> URL: https://issues.apache.org/jira/browse/HDFS-14878
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: hemanthboyina
> Assignee: hemanthboyina
> Priority: Major
> Attachments: HDFS-14878.001.patch
>
>
> {code:java}
> if (duration > dfsclientSlowLogThresholdMs) {
> LOG.info("Slow ReadProcessor read fields for block " + block
> + " took " + duration + "ms (threshold="
> + dfsclientSlowLogThresholdMs + "ms); ack: " + ack
> + ", targets: " + Arrays.asList(targets));
> } {code}
> log level should be warn here
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
