Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
MIME-Version: 1.0
In-Reply-To: <CANTWn9MgWS9aGjVb+vkJWj2U6w4u9RT5cpKB9n8PSm-da+2vWw@mail.gmail.com>
References: <CANTWn9MgWS9aGjVb+vkJWj2U6w4u9RT5cpKB9n8PSm-da+2vWw@mail.gmail.com>
From: Tom Crayford <tcrayford@heroku.com>
Date: Fri, 5 Aug 2016 15:34:30 +0100
Message-ID: <CAFXAVc4Qq4vS5D6sPEhJcRenUoQkO2waCKsskgvm=DQ7voi9KQ@mail.gmail.com>
Subject: Re: [DISCUSS] KIP-72 Allow Sizing Incoming Request Queue in Bytes
To: "dev@kafka.apache.org" <dev@kafka.apache.org>
Content-Type: multipart/alternative; boundary=001a114e6b3af1b8b9053953f667
archived-at: Fri, 05 Aug 2016 14:34:38 -0000

--001a114e6b3af1b8b9053953f667
Content-Type: text/plain; charset=UTF-8

This makes good sense to me, and seems to have very low amounts of downside
with large amounts of upside. +1

On Thursday, 4 August 2016, radai <radai.rosenblatt@gmail.com> wrote:

> Hello,
>
> I'd like to initiate a discussion about
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> 72%3A+Allow+Sizing+Incoming+Request+Queue+in+Bytes
>
> The goal of the KIP is to allow configuring a bound on the capacity (as in
> bytes of memory used) of the incoming request queue, in addition to the
> current bound on the number of messages.
>
> This comes after several incidents at Linkedin where a sudden "spike" of
> large message batches caused an out of memory exception.
>
> Thank you,
>
>    Radai
>

--001a114e6b3af1b8b9053953f667--