https://issues.apache.org/jira/browse/KAFKA-156 is filed for that feature.
Thanks,
Neha
On Fri, Mar 15, 2013 at 12:55 AM, Ryan Chan wrote:
> Hi,
>
> On Fri, Mar 15, 2013 at 1:18 PM, Neha Narkhede
> wrote:
> > Ryan,
> >
> > Have you tried configuring the num.retries option on the log4j produce
Hi,
On Fri, Mar 15, 2013 at 1:18 PM, Neha Narkhede wrote:
> Ryan,
>
> Have you tried configuring the num.retries option on the log4j producer ?
> When there is a temporary network glitch, it will retry sending the
> messages instead of losing them.
>
Memory is limited and this is our concern. (W
Ryan,
Have you tried configuring the num.retries option on the log4j producer ?
When there is a temporary network glitch, it will retry sending the
messages instead of losing them.
Thanks,
Neha
On Thursday, March 14, 2013, Ryan Chan wrote:
> Hi,
>
> We are currently using the Log4j appender to
Hi,
We are currently using the Log4j appender to write to the Kafka (on
machine on another datacenter), but problem occur when the network is
interrupted as the message is stored in memory.
Are there any local forwarder/client or similar solutions that can be
installed on the localhost and take c
