Hi Sönke,
Thanks for taking the time to review. I’ve put KIP-349 into hibernation.
Thanks also to everyone who participated in the discussion.
Best regards,
--
Nick
> On Jan 25, 2019, at 5:51 AM, Sönke Liebau
> <soenke.lie...@opencore.com.INVALID> wrote:
>
> a bit late to the party, sorry. I recently spent some time looking
> into this / a similar issue [1].
> After some investigation and playing around with settings I think that
> the benefit that could be gained from this is somewhat limited and
> probably outweighed by the implementation effort.
>
> The consumer internal are already geared towards treating partitions
> fairly so that no partition has to wait an undue amount of time and
> this can be further tuned for latency over throughput. Additionally,
> if this is a large issue for someone, there is always the option of
> having a dedicated consumer reading only from the control topic, which
> would mean that messages from that topic are received "immediately".
> For a Kafka Streams job it would probably make sense to create two
> input streams and then merging those as a first step.
>
> I think with these knobs a fairly large amount of flexibility can be
> achieved so that there is no urgent need to implement priorities.
>
> So my personal preference would be to set this KIP to dormant for now.
