Broker replication is available now and fully documented in the docs. This approach to availability has a lot of advantages discussed in that ticket and the one below. Personally, having tried both approaches, I think this is what most people should do (running a small highly available cluster well is easier than managing 10x as many persistent stores spread across all your application nodes).
There is, however, a prototype patch to add limited persistence to the producer. You can see it here: https://issues.apache.org/jira/browse/KAFKA-1955 -Jay On Tue, Mar 3, 2015 at 8:15 AM, sunil kalva <kalva.ka...@gmail.com> wrote: > Hi > Is there any way to spool messages to disk at publisher side when kafka > cluster is down or not reachable for publisher. If kafka doesn't support > this feature, what is the best practise to handle this failure scenario. > > I was referring one of the old jira link which is still open state : > https://issues.apache.org/jira/browse/KAFKA-156, Is there any plan to > support this in future or any alternatives. > > What is broker replication some one mentioned in the same jira, is there > any documentation for that ? > > please advise me on this, my entire design depends on this feature. > > t > Sunil Kalva >
