Timeline for Oozie Shell action Output data exceeds its limit [2048]
Current License: CC BY-SA 4.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 14, 2018 at 5:37 | comment | added | Prabhu | I used pipe symbol to reduce the output size like below .... hdfs dfs -put -f file hdfspath | grep zzzzzzz...... It worked Thanks | |
Nov 13, 2018 at 12:59 | vote | accept | Prabhu | ||
Nov 13, 2018 at 12:55 | comment | added | Prabhu | If i run that from terminal without oozie, its not generating any log. When i use oozie shell action only it produces output logs | |
Nov 13, 2018 at 12:53 | comment | added | Prabhu | So you are saying this command "hdfs dfs -put -f file hdfspath" generates output that exceeds 2kb right? I printed that output and its generating 18kb size of logs. | |
Nov 13, 2018 at 12:31 | comment | added | Amit Kumar |
Try executing your shell script without oozie from terminal and then see how much characters gets printed on the terminal console. Increase the oozie.action.max.output.data size more than that. It will work
|
|
Nov 13, 2018 at 12:29 | comment | added | Amit Kumar | What do you mean by file is huge? it does not depend on file size you are using in hdfs put command. It captures the characters that gets printed on the console when you execute your shell script. | |
Nov 13, 2018 at 12:23 | comment | added | Prabhu | Sorry Forgot to mention, I need "<capture-output/>" for next action. One more thing, even if i increase (oozie.action.max.output.data) size, the file will huge size. So it will make problem again. | |
Nov 13, 2018 at 12:05 | history | answered | Amit Kumar | CC BY-SA 4.0 |