Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 10 Sep 2013 09:59:53 +0000 (UTC)
From: "Mck SembWever (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12663440.1376407038848.107177.1378807193939@arcas>
In-Reply-To: <JIRA.12663440.1376407038848@arcas>
References: <JIRA.12663440.1376407038848@arcas>
Subject: [jira] [Commented] (CASSANDRA-5883) Switch to Logback
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CASSANDRA-5883?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13762916#comment-13762916 ]=20

Mck SembWever commented on CASSANDRA-5883:
------------------------------------------

Has log4j2 been considered?
Both log4j (old) and logback has awful java code in its internals using syn=
chronised blocks/methods.

log4j2 seems to take a large step forward here and ensures an application w=
on't lock up in the same way a log4j/logback application can. Such contenti=
on locks are not unusual once you increase logging  in any high concurrent =
application.

log4j2 can be more than 1000x times faster=E2=80=A6
http://logging.apache.org/log4j/2.x/manual/async.html#Performance

               =20
> Switch to Logback
> -----------------
>
>                 Key: CASSANDRA-5883
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5883
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core, Tools
>            Reporter: Jonathan Ellis
>            Assignee: Dave Brosius
>            Priority: Minor
>             Fix For: 2.1
>
>         Attachments: 0001-Additional-migration-to-logback.patch, 5883-1.t=
xt, 5883-additional1.txt, 5883.txt
>
>
> Logback has a number of advantages over log4j, and switching will be stra=
ightforward since we are already using the slf4j translation layer: http://=
logback.qos.ch/reasonsToSwitch.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira