Hello everyone,

we did implement a couple of custom MapReduce jobs which we plan to schedule 
using Oozie workflows in MapReduce actions.

All MR jobs are running fine outside of Oozie, but one of them is not.

The problem we have is that if those MR jobs are run inside Oozie nothing is 
get logged using the Log4J loggers that we are registering within the Mapper 
and Reducer classes using e.g. "private static final Logger logger = 
Logger.getLogger(TransformMapper.class);"
The logging works fine if the MR jobs are run outside of Oozie and logging 
messages appear in the task attempt logs, but not when they are run within 
Oozie.

Does anyone face similar issues?

Does anyone know a solution to this problem?

Maybe it is just a matter of configuring something somewhere appropriately.

Thanks in advance for your answers,

Tobias

--
Tobias B.

Reply via email to