apisix icon indicating copy to clipboard operation
apisix copied to clipboard

feat: Can the preheating capability be added to newly created pods?

Open Donghui0 opened this issue 2 years ago • 6 comments

Description

For the application of Java technology stack, directly accepting the full amount of traffic after the pod is healthy will cause excessive timeout problems. Can the initial weight be set smaller for newly created pods (including elastic expansion or rolling updates), and every certain interval Time increases until it returns to the default weight.

Donghui0 avatar Jan 15 '24 08:01 Donghui0

Basically you want to slowly increase the weight of an upstream from X to Y within a time period T after first connection. Am I right?

Revolyssup avatar Jan 16 '24 14:01 Revolyssup

@Donghui0 This slow start capability is currently not supported

Revolyssup avatar Jan 16 '24 15:01 Revolyssup

Keeping the issue open for track

Revolyssup avatar Jan 17 '24 09:01 Revolyssup

Sorry, this question should refer to apisix-ingress-controller project.

Donghui0 avatar Jan 18 '24 10:01 Donghui0

@Donghui0 Hi!

As an alternative, you can use balancing type EWMA.

Apisix supports this balancing mechanism (ewma). And it is very effective when new Java pods start under high load. The load is applied smoothly as the underside warms up.

We use EWMA and everything is ok.

Although I also support that a slow_start option would be nice to have.

nightguide avatar Jan 23 '24 05:01 nightguide

@Donghui0 Hi!

As an alternative, you can use balancing type EWMA.

Apisix supports this balancing mechanism (ewma). And it is very effective when new Java pods start under high load. The load is applied smoothly as the underside warms up.

We use EWMA and everything is ok.

Although I also support that a slow_start option would be nice to have.

Thank you very much. I'm testing the EWMA load balancing policy.

Donghui0 avatar Jan 30 '24 06:01 Donghui0