Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by nagarajanchinnasamy
, 1 year ago
step failed: (1/1) /tmp/swa/shredded, with job id: job_1437122465719_0010, please see cluster logs for failure messages
via Google Groups by varun reddy, 2 years ago
step failed: (1/1) /user/hashoutput, with job id: job_1440408860150_0008, please see cluster logs for failure messages
via Google Groups by Joao Correia, 1 year ago
step failed: (1/1) snowplow/bad_rows, with job id: job_1459794457549_0001, please see cluster logs for failure messages
via Google Groups by Jimit Modi, 1 year ago
step failed: (1/1) snowplow/bad_rows, with job id: job_1456920518439_0001, please see cluster logs for failure messages
via GitHub by vmuraliraju
, 1 year ago
step failed: (1/1) /test/vittabai, with job id: job_1453567420128_0001, please see cluster logs for failure messages
cascading.flow.FlowException: step failed: (1/1) /tmp/swa/shredded, with job id: job_1437122465719_0010, please see cluster logs for failure messages at cascading.flow.planner.FlowStepJob.blockOnJob(FlowStepJob.java:193) at cascading.flow.planner.FlowStepJob.start(FlowStepJob.java:137) at cascading.flow.planner.FlowStepJob.call(FlowStepJob.java:122) at cascading.flow.planner.FlowStepJob.call(FlowStepJob.java:42) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)