Hi Folks,
Canarying traffic is an excellent way of reducing the impact when
releasing a new release with a bug. Such canarying is somewhat easier
with a few queueing backends like sqs & redis. In sqs for example each
application container/instance of canary can self regulate how much
throughput th
force the configuration update?
> > >
> > > Cheers,
> > > Peter
> > >
> > > On Wed, 4 Nov 2020 at 18:39, Ning Zhang wrote:
> > >
> > > > if your new topics are not named "topic1" or "topic2", maybe you want
> > to
ation.
Thanks
On Fri, Oct 30, 2020 at 7:18 AM Devaki, Srinivas wrote:
>
> Hi Folks,
>
> I'm running mirror maker as a dedicated cluster as given in the
> mirrormaker 2 doc. but for some reason when I add new topics and
> deploy the mirror maker it's not detecting the new
Hi Folks,
I'm running mirror maker as a dedicated cluster as given in the
mirrormaker 2 doc. but for some reason when I add new topics and
deploy the mirror maker it's not detecting the new topics at all, even
the config dumps in the mirror maker startup logs don't show the newly
added topics.
I'
nd analyse them.
>
> On 2020/08/23 16:39:35, "Devaki, Srinivas"
> wrote:
> > Hi Folks,
> >
> > I’m trying to find the consumer group rebalancing events, so to plot how
> > much time consumer groups usually take in rebalancing during application
> >
Hi Folks,
I’m trying to find the consumer group rebalancing events, so to plot how
much time consumer groups usually take in rebalancing during application
deployments.
I’ve tried to check the logs of `server.log`, `controller.log`,
`state-change.log`. but couldn’t find anything about rebalancing
Also, want to clarify one more doubt,
is there any way for the client to explicitly trigger a rebalance without
dying itself?
On Thu, Jan 30, 2020 at 7:54 PM Devaki, Srinivas
wrote:
> Hi All,
>
> We have a set of logstash consumer groups running under the same set of
> instan
Hi All,
We have a set of logstash consumer groups running under the same set of
instances, we have decided to run separate consumer groups subscribing
multiple topics instead of running single consumer group for all topics(the
reasoning behind this decision is because of how our elasticsearch clus