The wiki is great place to record the results or make suggestions that require formatting and graphics to explain, but I think I prefer mailing lists for discussion.
So, let me repeat here a question I raised in the wiki, since I don't want it to get lost :) Is there a JIRA for the issues mentioned in the first background example? (closing socket and connection unsuccessful). I'll be more than happy to pick those up as they've made my life pretty painful. Gwen On Tue, Aug 26, 2014 at 7:21 PM, Joe Stein <joe.st...@stealth.ly> wrote: > Hi Guozhang thanks for kicking this off. I made some comments in the Wiki > (and we can continue the discussion there) but think this type of > collaborative mailing list discussion and confluence writeup is a great way > for different discussions about the same thing in different organizations > to coalesce together in code. > > This may also be a good place for folks looking to get their feet wet > contributing code to-do so. > > /******************************************* > Joe Stein > Founder, Principal Consultant > Big Data Open Source Security LLC > http://www.stealth.ly > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > ********************************************/ > > > On Tue, Aug 26, 2014 at 6:22 PM, Guozhang Wang <wangg...@gmail.com> wrote: > >> Hello all, >> >> We want to kick off some discussions about error handling and logging >> conventions. With a number of great patch contributions to Kafka recently, >> it is good time for us to sit down and think a little bit more about the >> coding style guidelines we have (http://kafka.apache.org/coding-guide.html >> ). >> >> People at LinkedIn have discussed a bit about some observed issues about >> the error handling and logging verboseness, and here is a summary of the >> bullet points covered: >> >> >> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Error+Handling+and+Logging >> >> We would like to collect as much comments as possible before we move ahead >> to those logging cleaning JIRAs mentioned in the wiki, so please feel free >> to shoot any thoughts and suggestions around this topic. >> >> -- Guozhang >>
