Java action doc:
http://oozie.apache.org/docs/4.1.0/WorkflowFunctionalSpec.html#a3.2.7_Java_
Action
In the java action, you can use
<java-opts>-Xmx ${xmx}</java-opts>
Here xmx is a variable with pre-set value. You can re-run the workflow by
overriding this parameter. See
http://oozie.apache.org/docs/4.1.0/DG_WorkflowReRun.html for more info on
re-runs
-Shwetha
On 31/03/15 12:33 pm, "Harshal Vora" <[email protected]> wrote:
>Dear Swetha,
>
>Are you referring <arg> tag in workflow for java class?
>Or are you talking about the <key,value> config file that is provided
>when you launch a new coordinator instance?
>
>Can you kindly provide an example or point me to any documentation
>regarding this.
>Appreciate your help.
>
>Thanks,
>Regards,
>
>Regards,
>Harshal Vora
>www.radiolocus.com
>
>On 03/31/2015 11:32 AM, Shwetha Shivalingamurthy wrote:
>> The workflow can be parameterised for jvm params or xmx value. You can
>> then rerun the workflow by overriding the parameter
>>
>> -Shwetha
>>
>>
>> On 28/03/15 7:10 am, "Harshal Vora" <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> Assume that we have a coordinator job which has already spawned and
>>> successfully run 100 instances of the workflow which contains JAVA
>>>jobs.
>>>
>>> Now if we want to rerun a particular instance say instance number 80 of
>>> the workflow.
>>>
>>> Is it possible to pass command line arguments to the Java main class
>>> while we rerun a particular instance?
>>>
>>> The requirement is that original job might have processed data for 10
>>> different clients at once, but we might only want to rerun for one
>>> particular client if there is discrepancy within the generated output.
>>> OR
>>> A particular instance has to process much larger data set then all the
>>> other regular data sets and in that scenario, we need to provide a
>>> higher -Xmx value.
>>>
>>> Regards,
>>>
>>> --
>>> Regards,
>>> Harshal Vora
>>> www.radiolocus.com
>>>
>
