----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72104/ -----------------------------------------------------------
(Updated Feb. 13, 2020, 6:19 p.m.) Review request for atlas and Bolke de Bruin. Repository: atlas Description ------- This patch enables logging to STDOUT from processes spawned through atlas_start.py or atlas_config.py scripts. For now, even if configured in log4j, logging to STDOUT was supressed (by redirecting to log files only). Diffs (updated) ----- distro/src/bin/atlas_admin.py 894e4da03 distro/src/bin/atlas_config.py f09026ff9 distro/src/bin/atlas_kafka_setup.py 146a7e509 distro/src/bin/atlas_kafka_setup_hook.py 6fdff740d distro/src/bin/atlas_start.py 963faf402 distro/src/bin/atlas_update_simple_auth_json.py f93207124 distro/src/bin/cputil.py 98a9dc36d distro/src/bin/quick_start.py 9e8b33c54 distro/src/bin/quick_start_v1.py e9997b1a2 Diff: https://reviews.apache.org/r/72104/diff/2/ Changes: https://reviews.apache.org/r/72104/diff/1-2/ Testing ------- The tests were concluded by: 1. Building & running Atlas locally with default log4j configuration and ENABLE_LOGGING_TO_CONSOLE variable set to true. 2. Building & running Atlas on Openshift with log4j configuration pushing everything to STDOUT and ENABLE_LOGGING_TO_CONSOLE variable set to true. In both scenarios logs were available both in the .out/.err files in the Atlas logdir (backwards compatibility), but at the same time I was able to see them in STDOUT of both running process (local installation) and pod (openshift deployment). Thanks, Mariusz Górski
