Affects Version/s: 0.14.0, 0.14.1, 0.14.2, 0.14.3, 0.14.4, 0.15.0, 0.15.1, 0.15.2, 0.15.3, 0.16.0, 0.16.1
Fix Version/s: 0.17.0
Stderr output from a streaming task is not collected until the MRErrorThread is started by PipeMapRed.startOutputThreads(), which is done on the first call to map() or reduce().
This makes it difficult to debug failures in starting up the task process. It can also lead to deadlock when a task receives no input keys but produces significant stderr output: the process will block on writing to stderr, while streaming will block waiting for the process to exit.
We should start the MRErrorThread when the process is forked, and then add the reporter later to enable stderr output serve as a keep-alive.
|Component/s||contrib/streaming [ 12310972 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Resolution||Fixed [ 1 ]|
|Status||Patch Available [ 10002 ]||Resolved [ 5 ]|
|Status||Patch Available [ 10002 ]||Open [ 1 ]|