I am having issues with the database sessions when the application is deployed in a micro-service architecture. Following is my technology stack:
Scenario when this is happening:
Whenever I do the canary deployment which brings in new server (pod) that have schema with new column, but, no table or column has been dropped I see session count starts to blow up in the old server (pods) that crosses the Database connection threshold.
In my debugging I realized the schema is updated when a request to the new service is made for the first time and not during the server start up, not sure if this is related.
What could be possible issues, and how can I avoid this?