Has anyone had issues with Vault dynamic MS SQL credential causing dead locks on the SQL server? It looks like Vault may wrap the creation statement in a transaction. I’ve observed if the create sql statement fails it can 1) cause vault-agent to infinitely request another cred and 2) eventually cause deadlocks on the sql server.
We have a ticket open on databases creating (more than one) account when an dynamic request comes through. What the current theory is that there is enough latency or load on the database that is causing a timeout on the request so vault is making another request but the database does end up creating the user anyway.
Sadly the follow up to this on “okay how do we fix it” has gone unanswered so far. Engineering is aware though.