Hi I remember there was a rational behind that:
https://issues.apache.org/jira/browse/CAMEL-18098 <https://issues.apache.org/jira/browse/CAMEL-18098> "As spooling to disk requires that the volume have space and the user has permission to write to disk etc. For container workloads this is not always the case." So better would be to explicitly enable if *really* required for large data streams which is not always the case? Babak > On 24 Nov 2022, at 14:59, Claus Ibsen <claus.ib...@gmail.com> wrote: > > Hi > > Yeah that is a good idea to overflow to disk. > You are welcome to create a JIRA and send a PR against main branch. > > How big streams are you processing btw ? > > On Thu, Nov 24, 2022 at 2:37 PM Michael Rambichler <mich...@rambichler.at> > wrote: > >> Hi all, >> >> with camel 3.18. stream caching is enabled by default. That's good. >> >> But we have realized that spooling is disabled by default. >> IMHO this can lead to unwanted OOM situations. Because from now on (>= >> 3.18.x) a big stream will be cached by default in memory. >> Or am I wrong? >> >> I would strongly suggest that we set the default of spoolEnabled also to >> true. >> >> What do you think? >> >> BR >> Michael >> > > > -- > Claus Ibsen > ----------------- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
