Details
Description
Running a simple workflow that have a shell action with capture-output enabled, the SShActionExecutor look at the wrong stdout file. This is the the command that I found in the log:
ssh o PasswordAuthentication=no -o KbdInteractiveDevices=no -o StrictHostKeyChecking=no -o ConnectTimeout=20 workflow@redhat5 cat oozie-oozi/0000008-140708170302737-oozie-oozi-W/fileProcessing-ssh/22350.0000008-140708170302737-oozie-oozi-W@fileProcessing@1.stdout
But the generated stdout file is `/home/instadoc/oozie-oozi/0000008-140708170302737-oozie-oozi-W/fileProcessing--ssh/22350.0000008-140708170302737-oozie-oozi-W@fileProcessing@0.stdout`
If you relaunch the action the ID that prepend the .stdout extension could vary (ie: @9.stdout, @4.stdout) but the SShActionExecutor looks always at @0.stdout.
Attachments
Attachments
Issue Links
- is broken by
-
OOZIE-1503 [DB optimization] revisit eagerLoadState at places
- Closed