[
https://issues.apache.org/jira/browse/HDFS-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942254#comment-16942254
]
Brahma Reddy Battula commented on HDFS-10303:
---------------------------------------------
{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}
As per below description, I feel this logLvel should be "WARN'. Please correct
me if I am wrong.
* *Info* - Generally useful information to log (service start/stop,
configuration assumptions, etc). Info I want to always have available but
usually don't care about under normal circumstances. This is my out-of-the-box
config level.
* *Warn* - Anything that can potentially cause application oddities, but for
which I am automatically recovering. (Such as switching from a primary to
backup server, retrying an operation, missing secondary data, etc.)
> DataStreamer#ResponseProcessor calculates packet ack latency incorrectly.
> -------------------------------------------------------------------------
>
> Key: HDFS-10303
> URL: https://issues.apache.org/jira/browse/HDFS-10303
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.7.2
> Reporter: Surendra Singh Lilhore
> Assignee: Surendra Singh Lilhore
> Priority: Major
> Fix For: 2.8.0, 3.0.0-alpha1
>
> Attachments: HDFS-10303-001.patch, HDFS-10303-002.patch
>
>
> Packets acknowledge duration should be calculated based on the packet send
> time.
--
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
