Hi Mohammad,
Thanks for the response. We are using Oozie 2.3.2. When I reported this,
there were no coordinator jobs running but we do see similar issues when
the coordinator jobs are running as well. I will try with the params you
mentioned and get back.
BTW, We also see these errors in the log
On Fri, 2013-02-22 at 08:25 -0800, Alejandro Abdelnur wrote:
Hi Alejandro,
> Clément, any luck?
Unfortunately I have not been able to find some free time to test your
proposal today. I will most likely not be able to do it before the end
of next week. I will report the outcome of the test on the
Clément, any luck?
On Thu, Feb 21, 2013 at 9:35 AM, Alejandro Abdelnur wrote:
> Hi Clément,
>
> The HADOOP_USER_NAME trick will work only in a non-secure cluster where
> you can be whoever you want just by setting that property. it will not work
> in a secure setup.
>
> The JavaAction has the sa
Tim,
No, it is not possible today. You may want to open a JIRA to initiate a
discussion on how we could do this.
Thx
On Thu, Feb 21, 2013 at 9:50 PM, Tim Goodman wrote:
> I have a workflow action with many sub-workflows. If it's possible, I'd
> like to handle errors in the parent workflow on
Hi,
What version of Oozie are you using? Do you have any coordinator job running?
You could bumped up the value for this two properties:
oozie.service.CallableQueueService.threads = 150
oozie.service.CallableQueueService.callable.concurrency = 60
Please let us know how does it go.
Regards,
