Hello,
Interesting case, but I’m curious:
The regular test profile didn’t exercise this method enough to show the bug
But if db failover ever happened before (on production) wouldn’t we notice the same behavior?
Or it was a first time
Type your question above this line.
Course: https://www.educative.io/collection/10370001/5839546094190592
Lesson: https://www.educative.io/collection/page/10370001/5839546094190592/6683571072270336
Hi @Paul1,
If the DB failover happened before production, the consequences might not be harsh, but we notice the same behavior as we see in production.
If we don’t close the connection, it will leak connection memory. The connection will remain active until the application server/web server is shut down, even if the user logs out.
There are more justifications. Suppose the database server has 10 connections open and 10 clients request the connection. If the database server grants all of them, and after their usage, they are not closed, the database server would not be able to provide any other connection for another request. For that reason, we need to close them - it is mandatory.
Furthermore, it might lead to some mischievous activities regarding the integrity of the database.
I hope I have answered your query; please let me know if you still have any confusion.
Thank You 
Hi @Abdul_Mateen,
Thanks for your answer!
May be I formulated unclear:) I was curious whether the same failover ever happened in the past. (Not before production on development/staging, but before on time)
If it was not the first time in production - then the consequences should roughly be the same? We should 've noticed all those unclosed connections and the same behavior
Thanks again!