From: Peter Nagy (Jr) [mailto:pn...@gratex.com]
Sent: 17 October 2018 16:23
To: users@camel.apache.org
Subject: Re: throttling/backpressure on a route
Hi Valdis,
and your MQ is throttling how? Serializing it to disk? Or is it keeping it in
RAM but running on a different machine?
It seems to be a
r since (still working fast enough for us).
>
>
> Regards,
> Valdis
>
> -Original Message-
> From: Peter Nagy (Jr) [mailto:pn...@gratex.com]
> Sent: 17 October 2018 15:09
> To: users@camel.apache.org
> Subject: Re: throttling/backpressure on a route
>
> H
er 2018 15:09
To: users@camel.apache.org
Subject: Re: throttling/backpressure on a route
Hi Onder,
Onder SEZGIN writes:
> Hi,
> I would suggest
> 1- Take a look at throttle-eip. (Make sure you understand split,
> aggregate and mongodb3 producer adocs around mongodb aggregation. Try
Hi Onder,
Onder SEZGIN writes:
> Hi,
> I would suggest
> 1- Take a look at throttle-eip. (Make sure you understand split, aggregate
> and mongodb3 producer adocs around mongodb aggregation. Try and see your
> case unless you can explain or create a unit test to pinpoint your issue
> and also che
Hi,
I would suggest
1- Take a look at throttle-eip. (Make sure you understand split, aggregate
and mongodb3 producer adocs around mongodb aggregation. Try and see your
case unless you can explain or create a unit test to pinpoint your issue
and also check mongodb3 components test case for better ex
Newbie question incoming.
I have a route that looks like
...
.setHeader("CamelMongoDbBatchSize", 128)
.to("mongodb3:mymongo?...&operation=aggregate&outputType=MongoIterable")
.split(constant(true))
.streaming()
...
.aggregate(constant(true), new GroupedBodyAggregationStrategy())
.completionSize(1
