Yes and no. We're running a version about a month behind trunk at any given time here at LinkedIn. That's generally the amount of time we spend testing and going through our release process internally (less if there are no problems). So it can be done.
That said, we also have several Kafka contributors and a committer who work on Kafka constantly here. When talking to others about how we run Kafka at LinkedIn, I usually say "we run trunk so you don't have to." Unless you have someone to track down and work on fixing the bugs, it's probably a good idea to stick with the release versions, unless you run in a development environment where you can tolerate failures and performance regressions. -Todd On Tue, Jun 23, 2015 at 2:59 AM, Achanta Vamsi Subhash < achanta.va...@flipkart.com> wrote: > I am planning to use for the producer part. How stable is trunk generally? > > -- > Regards > Vamsi Subhash > > -- > > > > ------------------------------------------------------------------------------------------------------------------------------------------ > > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If you have received this email in error please notify the system manager. > This message contains confidential information and is intended only for the > individual named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. Please notify the sender > immediately by e-mail if you have received this e-mail by mistake and > delete this e-mail from your system. If you are not the intended recipient > you are notified that disclosing, copying, distributing or taking any > action in reliance on the contents of this information is strictly > prohibited. Although Flipkart has taken reasonable precautions to ensure no > viruses are present in this email, the company cannot accept responsibility > for any loss or damage arising from the use of this email or attachments >
