title: Should I use oozie to run a MapReduce task forever?
body: <p>I have a mapReduce task (https://github.com/flopezluis/testing-hadoop) that reads the files in a folder and it appends them to a zip. I need to run this task forever, so when it finishes to process them, it should run again. I'm reading about  oozie but I'm not sure whether it's the best fit, because maybe it's too big for my problem. </p>
  
  <p>In case oozie is the best solution. If I write a coordinator to run every 10 minutes, what happens if the task takes more than 10 minutes, the coordinator waits to run the task again?</p>
  
  <p><strong>Explanation of the task</strong> </p>
  
  <p>The folder is always the same. There are differences zips files, one for key. The idea is to create the zip file step by step. I think this faster than create the zip file after all the files are procesed. 
  The files contain something like this:</p>
  
  <pre><code>&lt;info operationId="key1"&gt;
   DATA1
  &lt;/info&gt;
  &lt;info operationId="key1"&gt;
  DATA2
  &lt;/info&gt;
  &lt;info operationId="key2"&gt;
  DATA3
  &lt;/info&gt;
  </code></pre>
  
  <p>So the zips will be like this:</p>
  
  <p>key1.zip --> data1, data2</p>
  
  <p>key3.zip --> data3</p>
  
  <p>Thanks</p>