Suet
Suet

Reputation: 141

oozie coordinator jobs not starting at the given start time

I am using oozie coordinator for scheduling my hadoop jobs. I give the start time as 12:26, but it start after 8-9 hours and it complete all the remaining jobs according to frequency I given in my job property file.

Why this halt of 8 hours, still it is completing the remaining jobs using the startTime i given in the job.properties?

nameNode=hdfs://localhost:8020
jobTracker=localhost:8021
queueName=default

oozie.libpath=${nameNode}/user/oozie/share/lib
oozie.use.system.libpath=true
oozie.wf.rerun.failnodes=true


appPath=${nameNode}/user/user1/mr
oozie.wf.application.path=${appPath}



frequency=60
jobStart=2014-12-31T12:26Z
jobEnd=2015-12-16T23:00Z
timezone=GMT+0530

inputDir=${nameNode}/user/user1/input
outputDir=${nameNode}/user/user1/output

oozie.coord.application.path=${appPath}/coordinator.xml

coordinator.xml

<coordinator-app name="LogCoordinator" frequency="${frequency}" start="${jobStart}" end="${jobEnd}" timezone="${timezone}" xmlns="uri:oozie:coordinator:0.1">
<action>
<workflow>
<app-path>${appPath}</app-path>
</workflow>
</action>          
</coordinator-app>

Is there any timeZone Issue?

Upvotes: 0

Views: 3160

Answers (2)

singh
singh

Reputation: 1080

First you need to configure "oozie.processing.timezone" in the oozie-site.xml ,which has the default value as UTC. Change it to your desired timezone ( IST here ) by specifying (GMT+0530) as its value and restart oozie. Then you have to configure the coordinator.xml with timezone="IST" ( Or GMT+0530). And provide the startTime/endTime in coordinator.properties with the actual IST time. UTC timezone has the timeStamp format as (yyyy-MM-dd'T'HH:mm'Z') The format for specifying the time will now be changed to (yyyy-MM-dd'T'HH:mm+0530) i.e if you want your job to run at 05:30(IST) then the value for startTime in properties file will be ( 2018-10-07T05:30+0530 ). This has worked for me. Hope this helps.

Upvotes: 0

karthik
karthik

Reputation: 551

did you cross checked the GMT time to our IST time!! Make sure that the IST time to your jobstart variable.

Upvotes: 1

Related Questions