Hello
https://cwiki.apache.org/confluence/display/KAFKA/KIP-375%3A+Kafka+Clients+-+make+Metadata%23TOPIC_EXPIRY_MS+configurable
I'd like to introduce new feature for kafka client:
Making org.apache.kafka.clients.Metadata#TOPIC_EXPIRY_MS configurable
Here is KPI
Hello
I'd like to introduce new feature for kafka client:
Making org.apache.kafka.clients.Metadata#TOPIC_EXPIRY_MS configurable
Here is KPI
https://cwiki.apache.org/confluence/display/KAFKA/KIP-375%3A+Make+org.apache.kafka.clients.Metadata%23TOPIC_EXPIRY_MS+configurable
The problem is: if
https://cwiki.apache.org/confluence/display/KAFKA/KIP-375%3A+Kafka+Clients+-+make+Metadata%23TOPIC_EXPIRY_MS+configurable
I'd like to introduce new feature for kafka client:
Making org.apache.kafka.clients.Metadata#TOPIC_EXPIRY_MS configurable
The problem is: if application sends records to some
I'd like to introduce new feature for kafka client:
Making org.apache.kafka.clients.Metadata#TOPIC_EXPIRY_MS configurable
Here is KPI
https://cwiki.apache.org/confluence/display/KAFKA/KIP-375%3A+Make+org.apache.kafka.clients.Metadata%23TOPIC_EXPIRY_MS+configurable
The problem is: if application
This KIP is to make java kafka producer client 100% async.
This is very important for applications with low latency requirements.
https://cwiki.apache.org/confluence/display/ARIES/KIP-190+-+
Make+java+kafka+producer+asynchronous
But I put it into ARIES space because I don't have access rights for
omplexity and also with
> other use cases. If it is deemed like a worthy improvement by the
> community, your KIP and subsequent PR are likely to be accepted.
>
> Thanks,
> Apurva
>
>
>
> On Fri, Aug 11, 2017 at 4:23 PM, Pavel Moukhataev <m_pas...@mail.ru.invalid
> &g
omplexity and also with
> other use cases. If it is deemed like a worthy improvement by the
> community, your KIP and subsequent PR are likely to be accepted.
>
> Thanks,
> Apurva
>
>
>
> On Fri, Aug 11, 2017 at 4:23 PM, Pavel Moukhataev <m_pas...@mail.ru.invalid
> &g
te bound on the amount of time the application is
> willing to wait for messages to be acknowledged. By setting this low
> enough, you can always favor fresh messages over older ones. And when the
> brokers are unavailable or simply overloaded, that's the best you can do
> IMO.
>
> On
Hi
Sometimes kafka is used in nearly real-time java applications that has low
latency requirements. In that case it is very important to minify latency.
In kafka producer API there are two things that are done synchronously and
can be optimized:
- cluster metadata fetch
- wait for free memory
