DNS records not properly updated when a SLAVE is promoted to MASTER

LoreLLo's Avatar

LoreLLo

19 Aug, 2016 09:05 AM

In a farm configured with two mysql instances in the same AZ I've terminated the master and scalr promoted the existing slave to master.
After some minutes Scalr created a new slave mysql to obey to autoscaling configuration.
The problem is that dns records on configured domain are not correctly updated:
- (int|ext)-mysql-master points correctly to the current master (old slave) - (int|ext)-mysql-slave points to the master and to the new slave

This error is not present in scalr-dns records suggested as connection string:
- (int|ext).slave.mysql2.*******.scalr-dns.net points correctly only to the new slave

Let me now if you need farm/role id to investigate the problem
thanks in advance
Lorenzo

  1. 1 Posted by LoreLLo on 02 Sep, 2016 01:35 PM

    LoreLLo's Avatar

    Not direcly related to the bug, but I've noticed that the records in scalr-dns.net domains are created even when custom DNS is in use, so why Scalr doesn't create CNAMES to those records, instead of maintaining two A records?

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac