hadoop - Oozie hourly coordinator timing out on future actions -


at 5 minute mark of every hour, have data past hour loaded hdfs. thought setup coordinator job run @ 10 minute mark of every hour process data while doing check if directory hour exists. ends happening coordinator perform normal on past hour's data @ time of submission, continue working fine next 2 hours , future actions go 'waiting' 'timedout'. guess there default max limit how long action can stay in 'waiting'. seems bit counterintuitive time out limit apply actions @ absolute future time. anyway, here's sample of coordinator.xml. i'm looking suggestions on either how design in way makes more sense or on how raise default timeout.

<datasets>     <dataset name="hourly_cl" frequency="${coord:hours(1)}" initial-instance="2016-02-08t11:10z" timezone="pst">         <uri-template>hdfs://user/tzl/warehouse/incoming/logmessages.log.${year}${month}${day}/${hour}/</uri-template>         <done-flag></done-flag>     </dataset>     <dataset name="hourly_cl_out" frequency="${coord:hours(1)}" initial-instance="2016-02-05t11:10z" timezone="pst">         <uri-template>hdfs://user/tzl/warehouse/output/logmessages.log.${year}${month}${day}/${hour}/</uri-template>         <done-flag></done-flag>     </dataset> </datasets>  <input-events>     <data-in name="coordinput1" dataset="hourly_cl">         <instance>${coord:current(-1)}</instance>     </data-in> </input-events> <output-events>     <data-out name="clout" dataset="hourly_cl_out">         <instance>${coord:current(-1)}</instance>     </data-out> </output-events>  <action>     <workflow>         <app-path>${apppath}</app-path>     <configuration>         <property>             <name>inputpath</name>             <value>${coord:datain('coordinput1')}</value>         </property>         <property>             <name>outputpath</name>         <value>${coord:dataout('clout')}</value>         </property>     </configuration>     </workflow> </action>

also noticed while looking @ logs oozie checks every minute each data directory. in other words @ 18:01 it'll check these exists logmessages.log.20160208/18

logmessages.log.20160208/19

logmessages.log.20160208/20

logmessages.log.20160208/21

...

and @ 18:02 again it'll check logmessages.log.20160208/18

logmessages.log.20160208/19

logmessages.log.20160208/20

logmessages.log.20160208/21

...

this taking unnecessary cpu cycles. assumed setting frequency hour, smart enough not waste time checking future datasets when i've defined instance past hour's data: current(-1)

i solved issue simple property adjustment. introducing under coordinator-app

<coordinator-app name="cl_test" frequency="${coord:hours(1)}" start="..."   end="..." timezone="pst" xmlns="uri:oozie:coordinator:0.2">     <controls>         <timeout>1440</timeout>         <concurrency>2</concurrency>         <throttle>1</throttle>     </controls> ... ... </coordinator-app>

specifically, <throttle> property limits how many actions can put waiting status. setting 1, timeout time applies next action in 'waiting' status. <timeout> changes timeout limit 'waiting' actions, while believe <concurrency> limits how many actions can running @ once.


Comments

Post a Comment

Popular posts from this blog

java - pagination of xlsx file to XSSFworkbook using apache POI -

right in code, reading xlsx file, xssfworkbook, , writing database. but, when size of xlsx file increases, causes outofmemory error. can not increase server size, or divide xlsx file pieces. tried loading workbook using file (instead of inputstream), didn't either. i looking way read 10k rows @ time (instead of entire file @ once) , iteratively write workbook , database. is there way apache poi? poi contains called "eventmodel" designed purpose. it's mentioned in faq : the ss eventmodel package api reading excel files without loading whole spreadsheet memory. require more knowledge on part of user, reduces memory consumption more tenfold. based on awt event model in combination sax. if need read-only access, best way it. however, may want double check first if issue somewhere else. check out this item : i think poi using memory! can do? 1 comes quite lot, reason isn't might think. so, first thing check - what's source of prob...
Read more

Unlimited choices in BASH case statement -

consider simple bash snippet: case $option in 1) image=${options[0]%.tar} ;; 2) image=${options[1]%.tar} ;; 3) image=${options[2]%.tar} ;; 4) image=${options[3]%.tar} ;; *) echo "invalid option" exit 1 esac in real script numbers goes 30. makes pretty long. can somehow specify cases variable? something this: case $option in $i) image=${options[$(($i-1))]%.tar} any pointer appreciated. you can match against multiple patterns in single clause: case $option in 1|2|3: echo "$option one, 2 or three" ;; esac if still typing you, can use simple pattern matching: case $option in # following matches # - single-digit numbers 0-9 # - two-digit numbers starting either 1 or 2 # - number 30 [0-9]|[12][0-9]|30) image=${options[$(($option-1))]%.tar} ;; *) echo "invalid option" 1>&2 exit 1 esac
Read more

apache - How do I stop my index.php being run twice for every user -

we've got webapp initial html served using apache , php. i noticed index.php being run twice every request. seems caused / effected rewrite rules in our .htaccess - rewritecond %{http_host} ^(www\.|hotels\.)ourdomain\.com$ [nc,or] rewritecond %{server_name} ^(www\.|hotels\.)ourdomain\.com$ [nc] rewriterule (.*) http://ourdomain.com/$1 [r=301] rewriterule ^hotels/([^/]+)/?\??(.*)$ ?d=$1&$2 [qsa] the final rule moving parameter url path query string. i.e. http://ourdomain.com/hotels/vegas?someparam=1 becomes http://ourdomain.com?d=vegas&someparam=1 if go directly query string version index.php run once. if use url redirected, index.php run twice (i'm checking adding error_log('end of index.php') file). so example going http://ourdomain.com/hotels/paris hits file twice http://ourdomain.com?d=paris hits once. i've seen this question , had @ blog mentioned , , can't find empty string url's (i've tried using yslow process). ...
Read more