-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38997/#review101469
-----------------------------------------------------------



ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-log4j.xml
 (line 32)
<https://reviews.apache.org/r/38997/#comment158867>

    The same code is in hdfs-log4j, which is contatened with this one, before 
writting on disk.
    
    Is there really any purpose of this change?


- Andrew Onischuk


On Oct. 5, 2015, 12:28 p.m., Vitalyi Brodetskyi wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38997/
> -----------------------------------------------------------
> 
> (Updated Oct. 5, 2015, 12:28 p.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk and Dmytro Sen.
> 
> 
> Bugs: AMBARI-13311
>     https://issues.apache.org/jira/browse/AMBARI-13311
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Attached is the json used for creating the cluster.
> Steps to reproduce:
> 1. Bring up a cluster using attached blue print json
> 2. Login to ambari and make sure all services are up and running
> 3. Run a service check on yarn.
> Expected: service check should because the job submitted by service check 
> actually succeeds and error code received is 0
> Actual: service check fails due to log4j misconfigs
> Attached RM logs for reference that smoke test job succeeds.
> 
> 
> Diffs
> -----
> 
>   
> ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-log4j.xml
>  bbd2a3f 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-log4j.xml
>  b52af80 
> 
> Diff: https://reviews.apache.org/r/38997/diff/
> 
> 
> Testing
> -------
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

Reply via email to