The call to Kafka producer's partitionFor will fail when max.block.ms duration is reached.
Fixes #59 and replaces #121
Motivation:
Not sure why this setTimer had been implemented in the first place, maybe max.block.ms did not exist at the time, but this is no longer needed.
Calls to producer.send(...)producer.partitionsFor(...) are subject to the max.block.ms configuration parameter, and a TimeoutException will be fired past this duration.
Although the failure no longer gets fired twice (like mentioned before in #59 ), it could introduce some issue in cases the cluster is slow, or network is slow. Say an user HAS to configure max.block.ms to a value greater than 2000, the hardcoded setTimer would fire BEFORE max.block.ms gets reached, which could block some users.
The call to Kafka producer's
partitionForwill fail whenmax.block.msduration is reached. Fixes #59 and replaces #121Motivation:
Not sure why this
setTimerhad been implemented in the first place, maybemax.block.msdid not exist at the time, but this is no longer needed.Calls to
producer.send(...)producer.partitionsFor(...)are subject to themax.block.msconfiguration parameter, and aTimeoutExceptionwill be fired past this duration.Although the failure no longer gets fired twice (like mentioned before in #59 ), it could introduce some issue in cases the cluster is slow, or network is slow. Say an user HAS to configure
max.block.msto a value greater than 2000, the hardcodedsetTimerwould fire BEFOREmax.block.msgets reached, which could block some users.