ag.wan

Our service interface has a warm-up time of 5 minutes, and the weight of all pod nodes is set to the default value of 100.

1.consumer subscription status is normal 2. the URL weight or timestamp parameters haven’t changed after the provider registration. This rules out the two common issues mentioned earlier.

I suspect the issue lies here: every time the weight changes, current is reset to 0. During the 5-minute warm-up period, the provider's weight keeps changing, causing each calculation to...

You’re right — in my previous table I deliberately exaggerated the numbers to make the difference more visible. In a real production configuration, the totalWeight during the warm-up phase will...

> > once the new nodes’ weights reach a certain threshold (say, 30+ or higher), the combination of “more new nodes” + “continuously increasing weights” will cause requests to be...

Among this batch of newly started nodes, the ones that come up earliest will take more traffic. The reason is that whenever an old node is selected in the round-robin,...