Here We know the orchestrator takes care of read-only flag once we perform the failovers. but suppose our master node’s MySQL service is restarted due to accidentally or crash or OOM issue then once the MySQL service will be up on the master node, we will have to manually connect the node and disable the read-only flag, so the application can resume their write hits.
Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave.
If you need the EC2 instance usage for the long term and you will be going to utilize/run EC2 instance 24x7x365 then it is recommended, you can convert your normal on-demand EC2 instance into the reserved instance to reduce your hourly charges of an EC2 instance. Before explaining the steps ie how we can convert […]
— Login to the AWS console — Under “AWS Management Console” –> “AWS Services” –> “Find Services” enter EC2 then click on search result “EC2: Virtual Servers in the Cloud”. — Click on “Instances” section then select “Instances” — Select the instance and Copy the “Instance ID” for which we need to assign the elastic ip. — Click on “EC2 Dashboard” –> […]
— Login to the AWS console — Under “AWS Management Console” –> “AWS Services” –> “Find Services” enter EC2 then click on search result “EC2: Virtual Servers in the Cloud”. — Click on “Instances” section then select “Instances” — Click on “Launch Instance” — Under search box type “Ubuntu” and then press enter. Choose your […]
— Add/Rename hostname inside “/etc/hosts“ — Add/Rename hostname inside “/etc/hostname“ — Dynamically update the hostname as well — Reboot the system
Error Solution — Verify IAM user account have “CloudWatchFullAccess” policy attached. — Verify “AWSAccessKeyId” and “AWSSecretKey” are correctly placed inside the config file “awscreds.conf“. like below i.e. without any single or double quote.