Import jobs show error

Follow
Jee

Hi there,

I am pretty new to datameer. In my work place, we use datameer. I have started learning datameer. I just created a simple import job. For instance import a file from HDFS to Datameer. But, i am seeing ERROR in the status tab.

 

 INFO [2017-03-29 09:43:01.143] [qtp455888635-123495279] (JobTraceCollector.java:120) - Including single history artifact JOB_DEFINITION
 INFO [2017-03-29 09:43:01.149] [qtp455888635-123495279] (JobTraceCollector.java:126) - No artifacts of type JOB_DEFINITION do exist!
 INFO [2017-03-29 09:43:01.150] [qtp455888635-123495279] (JobTraceCollector.java:120) - Including single history artifact JOB_LOG
 INFO [2017-03-29 09:43:01.158] [qtp455888635-123495279] (JobTraceCollector.java:126) - No artifacts of type JOB_LOG do exist!
 INFO [2017-03-29 09:43:01.159] [qtp455888635-123495279] (JobTraceCollector.java:120) - Including single history artifact JOB_PLAN_ORIGINAL
 INFO [2017-03-29 09:43:01.161] [qtp455888635-123495279] (JobTraceCollector.java:126) - No artifacts of type JOB_PLAN_ORIGINAL do exist!
 INFO [2017-03-29 09:43:01.162] [qtp455888635-123495279] (JobTraceCollector.java:120) - Including single history artifact JOB_PLAN_COMPILED
 INFO [2017-03-29 09:43:01.164] [qtp455888635-123495279] (JobTraceCollector.java:126) - No artifacts of type JOB_PLAN_COMPILED do exist!
 INFO [2017-03-29 09:43:01.164] [qtp455888635-123495279] (JobTraceCollector.java:120) - Including single history artifact JOB_CONF
 INFO [2017-03-29 09:43:01.168] [qtp455888635-123495279] (JobTraceCollector.java:126) - No artifacts of type JOB_CONF do exist!
 INFO [2017-03-29 09:43:01.169] [qtp455888635-123495279] (JobTraceCollector.java:120) - Including single history artifact JOB_EXECUTION_TRACE
 INFO [2017-03-29 09:43:01.171] [qtp455888635-123495279] (JobTraceCollector.java:126) - No artifacts of type JOB_EXECUTION_TRACE do exist!
 INFO [2017-03-29 09:43:01.171] [qtp455888635-123495279] (JobTraceCollector.java:120) - Including single history artifact CLUSTER_JOBS
 INFO [2017-03-29 09:43:01.174] [qtp455888635-123495279] (JobTraceCollector.java:126) - No artifacts of type CLUSTER_JOBS do exist!
 INFO [2017-03-29 09:43:01.174] [qtp455888635-123495279] (JobTraceCollector.java:134) - Including multi history artifact ERROR_LOG
 INFO [2017-03-29 09:43:01.175] [qtp455888635-123495279] (JobTraceCollector.java:139) - No artifacts of type ERROR_LOG do exist!
 INFO [2017-03-29 09:43:01.176] [qtp455888635-123495279] (JobTraceCollector.java:134) - Including multi history artifact TASK_LOG
 INFO [2017-03-29 09:43:01.180] [qtp455888635-123495279] (JobTraceCollector.java:139) - No artifacts of type TASK_LOG do exist!
 INFO [2017-03-29 09:43:01.181] [qtp455888635-123495279] (JobTraceCollector.java:134) - Including multi history artifact JOB_INPUT_DEFINITION
 INFO [2017-03-29 09:43:01.196] [qtp455888635-123495279] (JobTraceCollector.java:139) - No artifacts of type JOB_INPUT_DEFINITION do exist!
 INFO [2017-03-29 09:43:01.197] [qtp455888635-123495279] (JobTraceCollector.java:134) - Including multi history artifact JOB_CONF_CLUSTER
 INFO [2017-03-29 09:43:01.201] [qtp455888635-123495279] (JobTraceCollector.java:139) - No artifacts of type JOB_CONF_CLUSTER do exist!

Please let me know the reason and how to resolve the issue.

 

Thanks,

 

0

Comments

1 comment

Date Votes
  • Joel Stewart

    Hi Jee! It seems that the Job Trace itself did not capture any data. Perhaps there is an underlying symptom that needs attention first. I'd recommend reviewing the <INSTALLDIR>/logs/conductor.log file for any errors or warnings.

    This could point us in the right direction to identify the root cause of the job failure and the absence of data in the Job Trace. 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post