After a bit more research I discovered that the lua scripts are actually from signal sciences.
You should have a conversation with Signal Sciences, and how they are doing ingress capture that goes through Haproxy. https://docs.signalsciences.net/install-guides/other-modules/haproxy-module/ Dave. p.s. Yes we did meet at KubeCon, and I really appreciated your suggestions on healthchecking. I just haven't had a chance to check/test them because of higher priority issues that have arisen *(isn't this always the case). And no this isn't even one fo those higher priority issues. On Wed, Dec 11, 2019 at 2:35 AM Baptiste <[email protected]> wrote: > > On Mon, Dec 2, 2019 at 5:15 PM Dave Chiluk <[email protected]> wrote: >> >> Since 2.0 nbproc and nbthreads are now mutually exclusive, are there >> any ways to make lua multi-threaded? >> >> One of our proxy's makes heavy use of lua scripting. I'm not sure if >> this is still the case, but in earlier versions of HAProxy lua was >> single threaded per process. Because of this we were running that >> proxy with nbproc=4, and nbthread=4. This allowed us to scale without >> being limited by lua. >> >> Has lua single-threaded-ness now been solved? Are there other options >> I should be aware of related to that? What's the preferred way around >> this? >> >> Thanks, >> Dave. >> > > Hi Dave, > (I think we met at kubecon) > > What's your use case for Lua exactly? > Can't it be replaced by SPOE at some point? (which is compatible with > nbthread and can run heavy processing outside of the HAProxy process)? > > You can answer me privately if you don't want such info to be public. > > Baptiste
