Kafka, mail # dev - fetch.wait.max.ms handling racy? - 2014-04-29, 20:02
Solr & Elasticsearch trainings in New York & San Francisco [more info][hide]
 Search Hadoop and all its subprojects:

Switch to Threaded View
Copy link to this message
fetch.wait.max.ms handling racy?
Am I missing something or is the handling of fetch.wait.max.ms racy? In 0.8 code I don't see any locking (might just be missing it) around the initial check to see if we can satisfy the event and enqueuing a delayed request in the purgatory, so if data arrives that satisfies the request it might be missed. Is that by design?

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB