We found an issue in one of our internal environments after one of our developers was testing token authentication and it failed when being sent through one server and not the other. We found that the DBVHACONN.txt file on one App server hadnt updated in over a month the files were out of sync between the 2.
Because of the out of date file 1 server beliveved replica1 was primary while the other thought replica2 was. I renamed the file that hadnt updated to get a new one to generate and it has resolved the problem but does anyone know how this can happen? and how we make sure it doesnt happen again?
Add a Comment
Please sign in on the right menu to comment.
If you do not have an account, please Join now.