[ 
https://issues.apache.org/jira/browse/OOZIE-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286551#comment-14286551
 ] 

Hadoop QA commented on OOZIE-1894:
----------------------------------

Testing JIRA OOZIE-1894

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:red}-1{color} the patch contains 4 line(s) longer than 132 
characters
.    {color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.    Tests run: 1569
.    Tests failed: 1
.    Tests errors: 1

.    The patch failed the following testcases:

.      testSparkAction(org.apache.oozie.action.hadoop.TestSparkActionExecutor)

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2190/

> Better error reporting to user
> ------------------------------
>
>                 Key: OOZIE-1894
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1894
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Purshotam Shah
>            Assignee: Purshotam Shah
>         Attachments: OOZIE-1894-V1.patch, OOZIE-1894-V2.patch, error.png
>
>
> Ooize debuggability is not that easy. We noticed most of user has difficulty 
> finding proper error message.
> They will create ticket to solution-team/dev to help.
> Though we have log streaming, but it flooded with other log messages. It's 
> very difficult for naive user to find out failure reason.
> Here is my solution,
> 1. Add a new appender to log only error message. Oozie appender will still 
> have all the log message ( including error).
> 2. Have a new UI tab ( cli/web-service as well) to show error message. When 
> user ask for error message, parse it from error logs. It will be faster.
> This has multiple advantage
> 1. Error log streaming will be faster.
> 2. User will see less and precise log, will help him to solve issue by his 
> own.
> 3. It will help ops/dev to find out system issues.
> New appender.
> {code}
> +log4j.appender.oozieError=org.apache.log4j.rolling.RollingFileAppender
> +log4j.appender.oozieError.RollingPolicy=org.apache.oozie.util.OozieRollingPolicy
> +log4j.appender.oozieError.File=${oozie.log.dir}/oozie-error.log
> +log4j.appender.oozieError.Append=true
> +log4j.appender.oozieError.layout=org.apache.log4j.PatternLayout
> +log4j.appender.oozieError.layout.ConversionPattern=%d{ISO8601} %5p %c{1}:%L 
> - SERVER[${oozie.instance.id}] %m%n
> +# The FileNamePattern must end with "-%d{yyyy-MM-dd-HH}.gz" or 
> "-%d{yyyy-MM-dd-HH}" and also start with the 
> +# value of log4j.appender.oozie.File
> +log4j.appender.oozieError.RollingPolicy.FileNamePattern=${log4j.appender.oozieError.File}-%d{yyyy-MM-dd-HH}
> +# The MaxHistory controls how many log files will be retained (720 hours / 
> 24 hours per day = 30 days); -1 to disable
> +log4j.appender.oozieError.RollingPolicy.MaxHistory=720
> +log4j.appender.oozieError.filter.1 = org.apache.log4j.varia.LevelMatchFilter
> +log4j.appender.oozieError.filter.1.levelToMatch = WARN
> +log4j.appender.oozieError.filter.2 = org.apache.log4j.varia.LevelMatchFilter
> +log4j.appender.oozieError.filter.2.levelToMatch = ERROR
> +log4j.appender.oozieError.filter.3 = org.apache.log4j.varia.LevelMatchFilter
> +log4j.appender.oozieError.filter.3.levelToMatch = FATAL
> +log4j.appender.oozieError.filter.4 = org.apache.log4j.varia.DenyAllFilter
> -log4j.logger.org.apache.oozie=INFO, oozie
> +log4j.logger.org.apache.oozie=ALL, oozie, oozieError
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to