update kafka version to 2.0.0.33 (linkedin#194)

Bypass large message processing when passthrough is enabled for consu…

…mer (linkedin#193)

Co-authored-by: Ke Hu <[email protected]>

Fix Kafka flush() contract different in vanilla client v/s li-apache-…

…kafka-clients (linkedin#192)

* Removed verifyOpen() from flush() and flush(long timeout, TimeUnit timeUnit).
* Peeled InnovationTargetException and re-throw vinilla client exception in flush().
* Added producer flush() test.
* Added testProducerFlushWithBrokerKilled.
* Fixed the comments.
* Changed exception handling and some flush test modification.

Update build.gradle (linkedin#191)

Bump kafka version from 2.0.0.28 to 2.0.0.29 to pick up fix for clust…

…er id check (linkedin#190)

Co-authored-by: Ke Hu <[email protected]>

Fix race condition in LiKafkaInstrumentedProducerImpl (linkedin#189)

* Fix race condition in LiKafkaInstrumentedProducerImpl when two threads calling close in send callback

Co-authored-by: Ke Hu <[email protected]>

Add new LiKafkaConsumerImpl metric - _offsetInvalidOrOutRangeCounter …

…to estimate the potential data loss (linkedin#185)

Added new metric( _offsetInvalidOrOutRangeCounter) into LiKafkaConsumerImpl to count number of OffsetOutOfRange exceptions under following cases with liclosest reset strategy.

1. fetchedOffset < Log Start Offset (LSO)
2. fetchedOffset <= Log End Offset (LEO)

This metric can be used as indicator to estimate the potential data loss upon the LiKafkaConsumer client reseting the offset to "liclosest"

pick latest kafka 2.0-li (linkedin#188)

Co-authored-by: Radai Rosenblatt <[email protected]>

bump conductor client, log conductor connection failures as warnings …

…for instrumented clients (linkedin#187)

Co-authored-by: Radai Rosenblatt <[email protected]>

add test and fix bugs of using payload.array() (linkedin#186)