[
https://issues.apache.org/jira/browse/MAPREDUCE-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527790#comment-14527790
]
Karthik Kambatla commented on MAPREDUCE-6354:
---------------------------------------------
I have the same concerns as Allen. We should also improve existing logs to
avoid logging for every connection.
bq. Allen, would it mitigate your concerns if this were logged with a
separately configurable logger, e.g.: ShuffleHandlerAuditLogger? That way users
could configure it on when they want to audit shuffle transfers or off when
they don't.
+1. Sounds like a good compromise. One could look at the shuffle connections if
they want to and roll up as aggressively as desired.
> shuffle handler should log connection info
> ------------------------------------------
>
> Key: MAPREDUCE-6354
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6354
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Chang Li
> Assignee: Chang Li
> Attachments: MAPREDUCE-6354.2.patch, MAPREDUCE-6354.3.patch,
> MAPREDUCE-6354.patch
>
>
> currently, shuffle handler only log connection info in debug mode, we want to
> log that info in a more concise way
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
