[jira] [Updated] (HDDS-3978) Switch log4j to log4j2 to avoid deadlock
[ https://issues.apache.org/jira/browse/HDDS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3978: - Description: We met dead lock related to log4j, the jstack information has been attached. For the following two reasons, I want to switch log4j in ozone and ratis to log4j2. 1. There are a lot of dead lock report in log4j: https://stackoverflow.com/questions/3537870/production-settings-file-for-log4j/ 2. And log4j2 is better than log4j. https://stackoverflow.com/questions/30019585/log4j2-why-would-you-use-it-over-log4j Besides log4j and log4j2 both exist in ozone, audit log use log4j2, and other log use log4j, maybe it's time to unify them. was: We met dead lock related to log4j, the jstack information has been attached. For the following two reasons, I want to switch log4j in ozone and ratis to log4j2. 1. There are a lot of dead lock report in log4j: https://stackoverflow.com/questions/3537870/production-settings-file-for-log4j/ 2. And log4j2 is better than log4j. https://stackoverflow.com/questions/30019585/log4j2-why-would-you-use-it-over-log4j > Switch log4j to log4j2 to avoid deadlock > > > Key: HDDS-3978 > URL: https://issues.apache.org/jira/browse/HDDS-3978 > Project: Hadoop Distributed Data Store > Issue Type: Improvement >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Attachments: jstack-deadlock-log.txt > > > We met dead lock related to log4j, the jstack information has been attached. > For the following two reasons, I want to switch log4j in ozone and ratis to > log4j2. > 1. There are a lot of dead lock report in log4j: > https://stackoverflow.com/questions/3537870/production-settings-file-for-log4j/ > 2. And log4j2 is better than log4j. > https://stackoverflow.com/questions/30019585/log4j2-why-would-you-use-it-over-log4j > Besides log4j and log4j2 both exist in ozone, audit log use log4j2, and other > log use log4j, maybe it's time to unify them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3978) Switch log4j to log4j2 to avoid deadlock
[ https://issues.apache.org/jira/browse/HDDS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3978: - Description: We met dead lock related to log4j, the jstack information has been attached. For the following two reasons, I want to switch log4j in ozone and ratis to log4j2. 1. There are a lot of dead lock report in log4j: https://stackoverflow.com/questions/3537870/production-settings-file-for-log4j/ 2. And log4j2 is better than log4j. https://stackoverflow.com/questions/30019585/log4j2-why-would-you-use-it-over-log4j was:We met dead lock related to log4j, the jstack information has been attached. > Switch log4j to log4j2 to avoid deadlock > > > Key: HDDS-3978 > URL: https://issues.apache.org/jira/browse/HDDS-3978 > Project: Hadoop Distributed Data Store > Issue Type: Improvement >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Attachments: jstack-deadlock-log.txt > > > We met dead lock related to log4j, the jstack information has been attached. > For the following two reasons, I want to switch log4j in ozone and ratis to > log4j2. > 1. There are a lot of dead lock report in log4j: > https://stackoverflow.com/questions/3537870/production-settings-file-for-log4j/ > 2. And log4j2 is better than log4j. > https://stackoverflow.com/questions/30019585/log4j2-why-would-you-use-it-over-log4j -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3978) Switch log4j to log4j2 to avoid deadlock
[ https://issues.apache.org/jira/browse/HDDS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3978: - Description: We met dead lock related to log4j, the jstack information has been attached. (was: We met dead lock related to log4j, the jstack information has been attached.) > Switch log4j to log4j2 to avoid deadlock > > > Key: HDDS-3978 > URL: https://issues.apache.org/jira/browse/HDDS-3978 > Project: Hadoop Distributed Data Store > Issue Type: Improvement >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Attachments: jstack-deadlock-log.txt > > > We met dead lock related to log4j, the jstack information has been attached. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3978) Switch log4j to log4j2 to avoid deadlock
[ https://issues.apache.org/jira/browse/HDDS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3978: - Description: We met dead lock related to log4j, the jstack information has been attached. > Switch log4j to log4j2 to avoid deadlock > > > Key: HDDS-3978 > URL: https://issues.apache.org/jira/browse/HDDS-3978 > Project: Hadoop Distributed Data Store > Issue Type: Improvement >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Attachments: jstack-deadlock-log.txt > > > We met dead lock related to log4j, the jstack information has been attached. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3978) Switch log4j to log4j2 to avoid deadlock
[ https://issues.apache.org/jira/browse/HDDS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3978: - Attachment: jstack-deadlock-log.txt > Switch log4j to log4j2 to avoid deadlock > > > Key: HDDS-3978 > URL: https://issues.apache.org/jira/browse/HDDS-3978 > Project: Hadoop Distributed Data Store > Issue Type: Improvement >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Attachments: jstack-deadlock-log.txt > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
