HashiCorp Consul 1.2: Service Mesh

Re:HashiCorp Consul 1.2: Service Mesh by tacticus on Tuesday June 26, 2018 @06:03AM (#17399238)

Old workers stay around until all the connections for them or their grace period has expired. So i hope you're not too close to the resource limit to handle many generations of workers sticking around. also if you have many services behind a single port with path based routing and do a deploy the connection will stick around on the old workers until everything dies.

It's super fun with haproxy :(

[ Parent | on HN ]

Re:HashiCorp Consul 1.2: Service Mesh by oblio on Tuesday June 26, 2018 @06:43AM (#17399400)

Kind of bad, but what's the alternative? Cut everyone off on reload?

[ Parent | on HN ]

Re:HashiCorp Consul 1.2: Service Mesh by tacticus on Tuesday June 26, 2018 @07:46AM (#17399714)

Have a better proxy that doesn't need to create a new generation of workers for config changes.

Like traefik or envoy or nginx when you pay for it or use the lua shit to do backend discovery (haproxy also has lua shit iirc)

[ Parent | on HN ]

Re:HashiCorp Consul 1.2: Service Mesh by pas on Tuesday June 26, 2018 @10:02AM (#17400646)

Could you elaborate on what's wrong with using lua with ningx, especially as used by kong?

[ Parent | on HN ]

Re:HashiCorp Consul 1.2: Service Mesh by timdumol on Tuesday June 26, 2018 @12:11PM (#17401802)

I think GP means Lua "shit" in a nonderogative manner (synonymous to Lua stuff).

[ Parent | on HN ]

Re:HashiCorp Consul 1.2: Service Mesh by pas on Tuesday June 26, 2018 @10:01AM (#17400635)

kong. uses lua. has a wonderful API.

[ Parent | on HN ]