Re: Lua + shared memory segment

2019-11-08 Thread Thierry Fournier
Hi, You can’t use socket in sample-fetches for HAProxy internal reason. If you want to take decision using socket+redis, you must set your Redis request in “action”. according with the redis response, your action set the result in shared context, and a sample fetche can return the result. Somethin

Fwd: Lua + shared memory segment

2019-11-07 Thread Kalantari
Hi Thierry, I know this an old thread but I'm having a similar issue where HA Proxy doesn't allow me to use Redis (not allowed to use socket in fetches). My scenario is as below: one frontend and multiple backends (proxies). (the frontend is just one IP and always sends requests to the same url)

Re: Lua + shared memory segment

2017-08-01 Thread bjun...@gmail.com
2017-08-01 10:47 GMT+02:00 Thierry Fournier : > >> On 31 Jul 2017, at 22:41, bjun...@gmail.com wrote: >> >> Hi, >> >> i'm experimenting with some Lua code in HAProxy where i need a simple >> key/value store (not persistent). I want to avoid Redis or other external >> dependency. >> >> Is there so

Re: Lua + shared memory segment

2017-08-01 Thread Thierry Fournier
> On 31 Jul 2017, at 22:41, bjun...@gmail.com wrote: > > Hi, > > i'm experimenting with some Lua code in HAProxy where i need a simple > key/value store (not persistent). I want to avoid Redis or other external > dependency. > > Is there some sort of shared memory segment in HAProxy Lua integ

Lua + shared memory segment

2017-07-31 Thread bjun...@gmail.com
Hi, i'm experimenting with some Lua code in HAProxy where i need a simple key/value store (not persistent). I want to avoid Redis or other external dependency. Is there some sort of shared memory segment in HAProxy Lua integration that can be used? (or is it possible to access HAProxy stick-table