Thanks! In the meanwhile, do you think simply modifying the producer to log the same message to multiple brokers (which are not part of a cluster) is a reasonably good solution to reduce the probability of lost messages? I have seen the mirroring documentation, but it sounded like the mirroring consumer was embedded inside the broker, and hence a dead broker will mean losing unflushed messages.
Thank you! -neelesh On Fri, May 18, 2012 at 3:26 PM, Neha Narkhede <neha.narkh...@gmail.com>wrote: > Hi Neelesh, > > Thank you for your interest in Kafka ! > > We are shooting for end of summer this year for the 0.8 release. You can > track the progress of this feature here - > https://issues.apache.org/jira/browse/KAFKA-50 > > Thanks, > Neha > > > On Fri, May 18, 2012 at 3:21 PM, Neelesh <neele...@gmail.com> wrote: > > > Hi, > > I am intrigued by the design of Kafka and pushing for using it in our > > org. We have many use cases where kafka fits the bill. Is there a > timeframe > > you are looking at for Kafka 0.8 to be released?I am especially > interested > > in long polling, (KAFKA-48) and thinking of writing a more sophisticated > > PHP client which can do producer side load balancing, and possible > > something like IronCount for the consumer side. > > > > Thanks! > > -neelesh > > >
