<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Oozie coordinator timezone in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-coordinator-timezone/m-p/162994#M36758</link>
    <description>&lt;P&gt;Okay, I found a workaround, I added:&lt;/P&gt;&lt;PRE&gt;-Duser.timezone=GMT&lt;/PRE&gt;&lt;P&gt;which changes the the JVM timezon. The final Flume-ng command will be as following:&lt;/P&gt;&lt;PRE&gt;flume-ng agent --conf-file spool1.properties --name agent1 --conf $FLUME_HOME/conf -Duser.timezone=GMT&lt;/PRE&gt;&lt;P&gt;The needed directory for the oozie coordiantor is now being created.&lt;/P&gt;</description>
    <pubDate>Wed, 03 Aug 2016 21:49:38 GMT</pubDate>
    <dc:creator>zaher_mahdhi</dc:creator>
    <dc:date>2016-08-03T21:49:38Z</dc:date>
    <item>
      <title>Oozie coordinator timezone</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-coordinator-timezone/m-p/162993#M36757</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I've created an Oozie coordinator with synchronous dataset. The time in the cluster  is set to CEST (GMT+2). I'm using flume to collect data and create a directory in HDFS in this format: &lt;/P&gt;&lt;PRE&gt;/flume/%Y/%m/%d/%H&lt;/PRE&gt;&lt;P&gt;coordinator.properties:&lt;/P&gt;&lt;PRE&gt;nameNode=hdfs://vm1.local:8020
jobTracker=vm1.local:8050
queueName=default
exampleDir=${nameNode}/user/root/oozie-wait

oozie.use.system.libpath = true

start=2016-08-03T08:01Z
end=2016-08-03T12:06Z
workflowAppUri=${exampleDir}/app

oozie.coord.application.path=${exampleDir}/app&lt;/PRE&gt;&lt;P&gt;coordiantor.xml:&lt;/P&gt;&lt;PRE&gt;&amp;lt;coordinator-app name="every-hour-waitForData" frequency="${coord:hours(1)}" start="${start}" end="${end}" timezone="UTC"
                 xmlns="uri:oozie:coordinator:0.1"&amp;gt;
&amp;lt;datasets&amp;gt;    
&amp;lt;dataset name="ratings" frequency="${coord:hours(1)}" initial-instance="${start}" timezone="Europe/Paris"&amp;gt;
    &amp;lt;uri-template&amp;gt;hdfs://vm1.local:8020/user/root/flume/${YEAR}/${MONTH}/${DAY}/${HOUR}&amp;lt;/uri-template&amp;gt;
  &amp;lt;/dataset&amp;gt;
&amp;lt;/datasets&amp;gt;

&amp;lt;input-events&amp;gt;
      &amp;lt;data-in name="coordInput1" dataset="ratings"&amp;gt;
        &amp;lt;instance&amp;gt;${coord:current(0)}&amp;lt;/instance&amp;gt;
      &amp;lt;/data-in&amp;gt;
   &amp;lt;/input-events&amp;gt;

        &amp;lt;action&amp;gt;
        &amp;lt;workflow&amp;gt;
            &amp;lt;app-path&amp;gt;${workflowAppUri}&amp;lt;/app-path&amp;gt;
            &amp;lt;configuration&amp;gt;
        &amp;lt;property&amp;gt;
              &amp;lt;name&amp;gt;wfInput&amp;lt;/name&amp;gt;
              &amp;lt;value&amp;gt;${coord:dataIn('coordInput1')}&amp;lt;/value&amp;gt;
            &amp;lt;/property&amp;gt;
                &amp;lt;property&amp;gt;
                    &amp;lt;name&amp;gt;jobTracker&amp;lt;/name&amp;gt;
                    &amp;lt;value&amp;gt;${jobTracker}&amp;lt;/value&amp;gt;
                &amp;lt;/property&amp;gt;
                &amp;lt;property&amp;gt;
                    &amp;lt;name&amp;gt;nameNode&amp;lt;/name&amp;gt;
                    &amp;lt;value&amp;gt;${nameNode}&amp;lt;/value&amp;gt;
                &amp;lt;/property&amp;gt;
                &amp;lt;property&amp;gt;
                    &amp;lt;name&amp;gt;queueName&amp;lt;/name&amp;gt;
                    &amp;lt;value&amp;gt;${queueName}&amp;lt;/value&amp;gt;
                &amp;lt;/property&amp;gt;
            &amp;lt;/configuration&amp;gt;
        &amp;lt;/workflow&amp;gt;
    &amp;lt;/action&amp;gt;
&amp;lt;/coordinator-app&amp;gt;

&lt;/PRE&gt;&lt;P&gt;When running this example flume creates the directory &lt;/P&gt;&lt;PRE&gt;/user/root/flume/2016/08/03/10/&lt;/PRE&gt;&lt;P&gt;But the coordinator is waiting for /user/root/flume/2016/08/03/08&lt;/P&gt;&lt;P&gt;Does any one knows how to make Flume creates the directory in UTC or the coordinator reads the correct directory . &lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Aug 2016 15:43:56 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-coordinator-timezone/m-p/162993#M36757</guid>
      <dc:creator>zaher_mahdhi</dc:creator>
      <dc:date>2016-08-03T15:43:56Z</dc:date>
    </item>
    <item>
      <title>Re: Oozie coordinator timezone</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-coordinator-timezone/m-p/162994#M36758</link>
      <description>&lt;P&gt;Okay, I found a workaround, I added:&lt;/P&gt;&lt;PRE&gt;-Duser.timezone=GMT&lt;/PRE&gt;&lt;P&gt;which changes the the JVM timezon. The final Flume-ng command will be as following:&lt;/P&gt;&lt;PRE&gt;flume-ng agent --conf-file spool1.properties --name agent1 --conf $FLUME_HOME/conf -Duser.timezone=GMT&lt;/PRE&gt;&lt;P&gt;The needed directory for the oozie coordiantor is now being created.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Aug 2016 21:49:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-coordinator-timezone/m-p/162994#M36758</guid>
      <dc:creator>zaher_mahdhi</dc:creator>
      <dc:date>2016-08-03T21:49:38Z</dc:date>
    </item>
  </channel>
</rss>

