This is because the non-zero exit status of streaming process was not
treated as failure until 0.17. In 0.17, you can specify the
configuration property "stream.non.zero.exit.is.failure" as "true", to
consider the non-zero exit as failure. From 0.18, the default value
for/ stream.non.zero.exit.is.failure' is true.
Thanks
Amareshwari
/Chris Dyer wrote:
Hi all-
I am using streaming with some c++ mappers and reducers. One of the
binaries I attempted to run this evening had a dependency on a shared
library that did not exist on my cluster, so it failed during
execution. However, the streaming framework didn't appear to
recognize this failure, and the job tracker indicated that the mapper
returned success, but did not produce any results. Has anyone else
encountered this issue? Should I open a JIRA issue about this? I'm
using Hadoop-17.2
Thanks-
Chris
