hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jungtaek Lim (Jira)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-7317) add-latency-info-in-mergepath-in-file-committer-ver1
Date Mon, 18 Jan 2021 07:46:00 GMT
Jungtaek Lim created MAPREDUCE-7317:

             Summary: add-latency-info-in-mergepath-in-file-committer-ver1
                 Key: MAPREDUCE-7317
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7317
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
          Components: client
            Reporter: Jungtaek Lim

We have been observed some occurrences of huge delay from file output committer V1, where
file output committer V2 is not an option.

While the root cause should have investigated on our side, there's another issue that there's
insufficient information to debug. Most likely the huge delay comes from mergePaths, but the
class only provides the "debug" log message to log the call itself with parameters, nothing
else. mergePaths has been called recursively which is harder to trace how much latency specific
directory takes to merge.

It would be nice and not intrusive to add latency info in mergePath, so that we can see how
much latency specific directory takes to merge, only when debug log is enabled.

(Ideally it'd be nice if we can log warn message when the call takes huge time to process,
but I don't have the proper threshold for the "huge time", so I'd avoid dealing with it altogether

This message was sent by Atlassian Jira

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

View raw message