On Thu, Jan 15, 2015 at 7:12 PM, Rainer Gerhards <[email protected]> wrote: [...]
> 2. provide a general infrastructure for pull models, whatever this is to be > used for > > [...] > Use cases for 2 exists, but I don't know the specifics. They surface every > now and then on the ML when someone ask for pull integration. I think there > was even a discussion with Radu, but I may be wrong. > I remember some discussions, for example if rsyslog could buffer and expose an API, one could easily implement a plugin (say, on top of Elasticsearch) that would enable the datastore to pull in data at its own pace. This contrasts with the current push model, where one has to tune things like batch sizes and retries in a way that doesn't overall the destination. Which is not really possible, because you can't control the load generated by queries, GC, and whatnot. Of course the pull model has its own caveats, but it would be nice to be able to choose what works best for every usecase. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
