You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by Jon <jo...@gmail.com> on 2013/11/11 22:09:52 UTC
Future of Logback?
With the switch of Storm to Apache, are there any plans to move away from
Logback?...mainly pressure from Apache to switch to Apache Log4j2? Just
curious as this sort of pressures our application to use one logger or
another for non-Storm components.
Re: Future of Logback?
Posted by Ted Dunning <te...@gmail.com>.
+1 to what Michael says
Drill is using logback and there has been zero pressure to move to another
framework.
On Mon, Nov 11, 2013 at 10:15 PM, Michael Rose <mi...@fullcontact.com>wrote:
> I believe when Jon says "log4j" he refers to log4j2. Log4j2 is yet another
> successor to log4j, which claims to solve issues in logback. I wasn't able
> to discern a difference without log4j's usage of Disruptor (3.x).
>
> Michael Rose (@Xorlev <https://twitter.com/xorlev>)
> Senior Platform Engineer, FullContact <http://www.fullcontact.com/>
> michael@fullcontact.com
>
>
> On Mon, Nov 11, 2013 at 2:41 PM, Patricio Echagüe <pa...@gmail.com>wrote:
>
>> Logback if I'm not wrong was created by the creators of log4j and it's
>> more efficient and modern. What would be the rationale to switch to log4j?
>>
>> Sent from my Nexus 4.
>> On Nov 11, 2013 6:14 PM, "P. Taylor Goetz" <pt...@gmail.com> wrote:
>>
>>> No, and I doubt there would be any pressure to switch to log4j. If you
>>> look at the logback website[1] there are many Apache projects using it.
>>>
>>> [1] http://logback.qos.ch
>>>
>>>
>>> On Nov 11, 2013, at 4:09 PM, Jon <jo...@gmail.com> wrote:
>>>
>>> > With the switch of Storm to Apache, are there any plans to move away
>>> from Logback?...mainly pressure from Apache to switch to Apache Log4j2?
>>> Just curious as this sort of pressures our application to use one logger or
>>> another for non-Storm components.
>>>
>>>
>
Re: Future of Logback?
Posted by Michael Rose <mi...@fullcontact.com>.
I believe when Jon says "log4j" he refers to log4j2. Log4j2 is yet another
successor to log4j, which claims to solve issues in logback. I wasn't able
to discern a difference without log4j's usage of Disruptor (3.x).
Michael Rose (@Xorlev <https://twitter.com/xorlev>)
Senior Platform Engineer, FullContact <http://www.fullcontact.com/>
michael@fullcontact.com
On Mon, Nov 11, 2013 at 2:41 PM, Patricio Echagüe <pa...@gmail.com>wrote:
> Logback if I'm not wrong was created by the creators of log4j and it's
> more efficient and modern. What would be the rationale to switch to log4j?
>
> Sent from my Nexus 4.
> On Nov 11, 2013 6:14 PM, "P. Taylor Goetz" <pt...@gmail.com> wrote:
>
>> No, and I doubt there would be any pressure to switch to log4j. If you
>> look at the logback website[1] there are many Apache projects using it.
>>
>> [1] http://logback.qos.ch
>>
>>
>> On Nov 11, 2013, at 4:09 PM, Jon <jo...@gmail.com> wrote:
>>
>> > With the switch of Storm to Apache, are there any plans to move away
>> from Logback?...mainly pressure from Apache to switch to Apache Log4j2?
>> Just curious as this sort of pressures our application to use one logger or
>> another for non-Storm components.
>>
>>
Re: Future of Logback?
Posted by Patricio Echagüe <pa...@gmail.com>.
Logback if I'm not wrong was created by the creators of log4j and it's more
efficient and modern. What would be the rationale to switch to log4j?
Sent from my Nexus 4.
On Nov 11, 2013 6:14 PM, "P. Taylor Goetz" <pt...@gmail.com> wrote:
> No, and I doubt there would be any pressure to switch to log4j. If you
> look at the logback website[1] there are many Apache projects using it.
>
> [1] http://logback.qos.ch
>
>
> On Nov 11, 2013, at 4:09 PM, Jon <jo...@gmail.com> wrote:
>
> > With the switch of Storm to Apache, are there any plans to move away
> from Logback?...mainly pressure from Apache to switch to Apache Log4j2?
> Just curious as this sort of pressures our application to use one logger or
> another for non-Storm components.
>
>
Re: Future of Logback?
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
No, and I doubt there would be any pressure to switch to log4j. If you look at the logback website[1] there are many Apache projects using it.
[1] http://logback.qos.ch
On Nov 11, 2013, at 4:09 PM, Jon <jo...@gmail.com> wrote:
> With the switch of Storm to Apache, are there any plans to move away from Logback?...mainly pressure from Apache to switch to Apache Log4j2? Just curious as this sort of pressures our application to use one logger or another for non-Storm components.