atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ashutosh Mestry <ames...@hortonworks.com>
Subject Review Request 61200: ATLAS-1996: Log4J Default Configuration Updated
Date Fri, 28 Jul 2017 02:55:13 GMT

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

Review request for atlas and Madhan Neethiraj.


Bugs: ATLAS-1996
    https://issues.apache.org/jira/browse/ATLAS-1996


Repository: atlas


Description
-------

**Problem**
Existing log4J configuration did not include max size parameter. This caused logs to grow
making it hard for human log readers.

Another contributing factor to log size growth is TitanDB's _IndexSerializer_. When this is
used, the query conversion from graph query to indexed query is written as info log entry.

With the recent changes, many more index queries are used, thus contributing to growth of
log files.

**Solution**

Added maxFileSize parameter.
Changed _com.thinkaurelius.titan_ log level to _warn_.

**Additional Info**
Defaults need to be set in _Ambari_ so that they reflect correctly as part of deployment.


Diffs
-----

  addons/hive-bridge/src/main/resources/atlas-hive-import-log4j.xml c1184e5 
  distro/src/conf/atlas-log4j.xml a0ef6a9 
  typesystem/src/main/resources/atlas-log4j.xml c30403e 


Diff: https://reviews.apache.org/r/61200/diff/1/


Testing
-------

**Functional tests**
Observed configuration changes in the logs generated.


Thanks,

Ashutosh Mestry


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message