Correct. For no data loss, prefer embedded agent (but that too is limited
capacity).


On Sun, Feb 23, 2014 at 4:14 PM, Roshan Naik <[email protected]> wrote:

> When append() throws an exception it is cascaded back to the application
> and it needs to handle that and perhaps log elsewhere ?
>
> Seems like it can be difficult to guarantee no data loss with
> log4jAppender. Consequently embedded agent would be a better alternative
> when it is critical to have no data loss ?
> -roshan
>
>
> On Sat, Feb 22, 2014 at 9:49 PM, Hari Shreedharan <
> [email protected]
> > wrote:
>
> > Roshan,
> >
> > Please see inline.
> >
> >
> > Thanks,
> > Hari
> >
> >
> > On Saturday, February 22, 2014 at 9:20 PM, Roshan Naik wrote:
> >
> > > anyone ?
> > >
> > >
> > > On Thu, Feb 20, 2014 at 4:45 PM, Roshan Naik <[email protected]
> (mailto:
> > [email protected])> wrote:
> > >
> > > >
> > > > 1) Would it be right to say that the log4jappender will block till
> the
> > > > event is delivered to the flume agent ? basically wondering if this
> > impacts
> > > > the application that is writing the logs when the target flume agent
> is
> > > > taking time to accept the events.
> > > >
> > Yes it will wait until the message is delivered.
> > > >
> > > > 2) if the target flume agent is not available, it appears to me that
> > the
> > > > events will be dropped by log4j appender ?
> > > >
> > >
> > >
> > >
> >
> > Only in unsafe mode, else it will throw.
> > > >
> > > > i assume the answer is the same for either the LB and non-LB version
> of
> > > > the appender...
> > > > -roshan
> > > >
> > >
> > >
> > > --
> > > CONFIDENTIALITY NOTICE
> > > NOTICE: This message is intended for the use of the individual or
> entity
> > to
> > > which it is addressed and may contain information that is confidential,
> > > privileged and exempt from disclosure under applicable law. If the
> reader
> > > of this message is not the intended recipient, you are hereby notified
> > that
> > > any printing, copying, dissemination, distribution, disclosure or
> > > forwarding of this communication is strictly prohibited. If you have
> > > received this communication in error, please contact the sender
> > immediately
> > > and delete it from your system. Thank You.
> > >
> > >
> >
> >
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to