The reason for the change is the following. If the timeout is caused by a problem at the broker, It's actually not very useful to set the timeout too small. After timing out, the producer is likely to resend the data. This adds more load to the broker and will make the broker in a worse state. The only concern with a large timeout is that in case of a machine crash (not just jvm crash), the client may take up to the timeout time to realize there is a problem with the broker. However, this is relatively rare. So, a 10 sec timeout is probably still reasonable.
Jun On Sun, Oct 6, 2013 at 11:57 PM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext