hard20 pts · first answer countscloud-databasesdnstroubleshooting

App writes to old primary after failover

An Aurora failover finished in about 30 seconds, but a Java service kept trying to reach the old primary for 10 minutes. What is the most likely cause?

A.Aurora failovers always take about 10 minutes to fully completeB.The JVM cached the old DNS answer far longer than its TTLC.A security group change during failover blocked the new primaryD.The cluster endpoint always points to a reader after failover

Discussion 0

Join free to post in the discussion.

App writes to old primary after failover

Discussion 0

Related questions