CODEWITHSUNDEEP
javagoogle-app-enginegoogle-compute-enginegoogle-cloud-platform
bentzy
bentzy

Reputation: 1254

Google App Engine Scheduler will not route requests to all available instances

I have a running production environment (JAVA Spring MVC based) on Google App Engine. I've configured 1 resident F4 instance with 1 minimum instance. During normal times I have 2 instances, one resident and another dynamic. When there is more demand to the server app engine fires a new instance but will not direct requests to it and just keeps it running, sometimes for days:

App Engine Instances

This is the configuration in the old console:

App Engine Old Console

I did another test and configured 3 minimum instances The instances fire, but still no requests are directed to them :( Any ideas?

enter image description here

Upvotes: 1

Views: 145

Answers (1)

caskey
caskey

Reputation: 12725

Setting your maximum idle instances to 1 will force it to collect all but 1 of the idle instances. The problem may be that it appears all the requests are going to the first 'dynamic' instance, the 'resident' instance is idle and therefore there is 1 'idle-dynamic' instance. That strikes me as the likely logic that is producing the observed effects.

Upvotes: 1

Related Questions