[
https://issues.apache.org/jira/browse/HADOOP-16206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320140#comment-17320140
]
Ahmed Hussein edited comment on HADOOP-16206 at 4/13/21, 12:39 PM:
-------------------------------------------------------------------
Thanks [~weichiu] and [~zhangduo] for the suggestions. The approach of breaking
this up seems a good idea.
I propose a slightly different scheme of breaking-up the migration.
Instead of "per-module", the migration would be split into two phases:
# Phase-1: Get it to work. Straightforward replacement of log4j
** IMHO, it will be better to aim for log4j2 skipping the bridge API.
** Reviewer only needs to check that the tests pass and the new
configurations are not causing inconsistence.
** this implies that suggestions for tuning/enhancements should be noted but
not immediately applied.
# Phase-2: Post migration. Tuning and optimizations
** After the migration is done, separate Jiras are filed to tune the logging.
** Separate tickets can be issued to address performance evaluations and
exploration of other features such as Async, garbage-free, etc..
The approach of two-phases migration will reduce the burden and logically
separate between actual migration Vs. addressing suggestions and tuning
requests.
was (Author: ahussein):
Thanks [~weichiu] and [~zhangduo] for the suggestions. The approach of breaking
this up seems a good idea.
I propose a slightly different scheme of breaking-up the migration.
Instead of "per-module", the migration would be split into two phases:
# Phase-1: Get it to work. Straightforward replacement of log4j
** IMHO, it will be better to aim for log4j2 skipping the bridge way.
** Reviewer only needs to check that the tests pass and the new
configurations are not causing inconsistence.
** this implies that suggestions for tuning/enhancements should be noted but
not immediately applied.
# Phase-2: Post migration. Tuning and optimizations
** After the migration is done, separate Jiras are filed to tune the logging.
** Separate tickets can be issued to address performance evaluations and
exploration of other features such as Async, garbage-free, etc..
The approach of two-phases migration will reduce the burden and logically
separate between actual migration Vs. addressing suggestions and tuning
requests.
> Migrate from Log4j1 to Log4j2
> -----------------------------
>
> Key: HADOOP-16206
> URL: https://issues.apache.org/jira/browse/HADOOP-16206
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 3.3.0
> Reporter: Akira Ajisaka
> Priority: Major
> Attachments: HADOOP-16206-wip.001.patch
>
>
> This sub-task is to remove log4j1 dependency and add log4j2 dependency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
