Re: Introducing Dory

2016-06-13 Thread Jason J. W. Williams
t; > > Regards, > Dave > > > -Original Message- > From: "Jason J. W. Williams" > Sent: Monday, June 13, 2016 10:45am > To: users@kafka.apache.org > Subject: Re: Introducing Dory > > Hi Dave, > > Dory sounds very exciting. Without persiste

Re: Introducing Dory

2016-06-13 Thread Dave Peterson
apache.org Subject: Re: Introducing Dory On Mon, Jun 13, 2016 at 11:45:13AM -0600, Jason J. W. Williams wrote: > Hi Dave, > > Dory sounds very exciting. Without persistence its less useful for clients > connected over a WAN, since if the WAN goes wonky you could build up quite > a queue

Re: Introducing Dory

2016-06-13 Thread Pete Wright
On Mon, Jun 13, 2016 at 11:45:13AM -0600, Jason J. W. Williams wrote: > Hi Dave, > > Dory sounds very exciting. Without persistence its less useful for clients > connected over a WAN, since if the WAN goes wonky you could build up quite > a queue until it comes back. > I was thinking the same thi

Re: Introducing Dory

2016-06-13 Thread Dave Peterson
- From: "Jason J. W. Williams" Sent: Monday, June 13, 2016 10:45am To: users@kafka.apache.org Subject: Re: Introducing Dory Hi Dave, Dory sounds very exciting. Without persistence its less useful for clients connected over a WAN, since if the WAN goes wonky you could build up quite a

Re: Introducing Dory

2016-06-13 Thread Jason J. W. Williams
formation, then in the event of a machine crash, we > know that any resulting message loss is limited to messages with > timestamps > T, where T is the latest commit point. > > I hope this helps answer your questions, and that I haven't inundated > you with too much information

Re: Introducing Dory

2016-06-13 Thread Dave Peterson
t commit point. I hope this helps answer your questions, and that I haven't inundated you with too much information. Let me know if you have more questions. Regards, Dave -Original Message- From: "Arya Ketan" Sent: Sunday, June 12, 2016 11:52am To: users@kafka.apache.

Re: Introducing Dory

2016-06-12 Thread Arya Ketan
Hi Dave, Dory looks pretty interesting. I had a few further questions on it a) How does Dory handle kernel panics? b) What kind of message guarantees does dory provide and also if you can share some design decisions taken to enable the guarantees whatever they are. Thanks Arya Arya On Sun, Jun

Re: Introducing Dory

2016-06-12 Thread Dave Peterson
Thanks! Enjoy :-) On 6/12/2016 12:24 AM, Gwen Shapira wrote: Dory is pretty cool (even though it is named after a somewhat dorky fish). Thank you for sharing :) On Sun, Jun 12, 2016 at 1:24 AM, Dave Peterson wrote: Hello Kafka users, Version 1.1.0 of Dory is now available. See https://git

Re: Introducing Dory

2016-06-12 Thread Gwen Shapira
Dory is pretty cool (even though it is named after a somewhat dorky fish). Thank you for sharing :) On Sun, Jun 12, 2016 at 1:24 AM, Dave Peterson wrote: > Hello Kafka users, > > Version 1.1.0 of Dory is now available. See > https://github.com/dspeterson/dory for details. Dory is the successor

Re: Introducing Dory

2016-06-11 Thread Dave Peterson
There is an option for writing messages to a local log file, but this is intended purely for troubleshooting. Dory's intended purpose is to get messages off the local machine as quickly and efficiently as possible, and let the Kafka brokers handle the persistence. When a client sends a message

Re: Introducing Dory

2016-06-11 Thread Tauzell, Dave
Does Dory have the option to persist messages to local disk after the Dory ack but before sending to Kafka? Dave > On Jun 11, 2016, at 17:23, Dave Peterson wrote: > > Hello Kafka users, > > Version 1.1.0 of Dory is now available. See > https://github.com/dspeterson/dory for details. Dory is t

Introducing Dory

2016-06-11 Thread Dave Peterson
Hello Kafka users, Version 1.1.0 of Dory is now available. See https://github.com/dspeterson/dory for details. Dory is the successor to Bruce (https://github.com/tagged/bruce), a Kafka producer daemon I created while working at if(we) (http://www.ifwe.co/). The code has seen a number of improve