Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
0.8.2.0
-
None
-
None
Description
While debugging a system test, I observed the following.
1. A broker side configuration (replica.fetch.wait.max.ms=500,replica.fetch.min.bytes=4096) made the time to complete a produce request long (each taking about 500ms with ack=-1).
2. The producer client has a bunch of outstanding produce requests queued up on the brokers.
3. One of the brokers fails and we force updating the metadata.
4. The metadata request is queued up behind those outstanding producer requests.
5. By the time the metadata response comes back, some messages have failed all retries because of stale metadata.