You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Prabhu Joseph (Jira)" <ji...@apache.org> on 2023/01/05 07:52:00 UTC

[jira] [Assigned] (OOZIE-3712) Oozie Verbose Option at Workflow Level which sets Java Verbose to all JVMs involved in the actions

     [ https://issues.apache.org/jira/browse/OOZIE-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prabhu Joseph reassigned OOZIE-3712:
------------------------------------

    Assignee: Prabhu Joseph

> Oozie Verbose Option at Workflow Level which sets Java Verbose to all JVMs involved in the actions
> --------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-3712
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3712
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: Prabhu Joseph
>            Assignee: Prabhu Joseph
>            Priority: Major
>
> The most common issue in Oozie is NoSuhMethodError. And the best way to debug is to set the JVM option -verbose to the right JVM which has failed. The challenge is to identify which JVM failed and what is the OPTS option through which -verbose can be set. In MapReduce Action, MRAppMaster, MapTask and ReduceTask each have different way of passing OPTS. In Spark Action, Spark ApplicationMaster, Driver and Executors have different way of passing OPTS.
> This Jira intends to expose one config say oozie.workflow.enable.verbose=true in job.properties to user and internally Oozie sets -verbose to all the JVMs involved in the Actions (SparkAction, SqoopAction or MapReduceAction). This will be very useful for debugging the most common issue NoSuhMethodError.
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)