Quantcast
Channel: MySQL Forums - Replication
Viewing all 1562 articles
Browse latest View live

Replication Monitoring with the Performance Schema (no replies)


Promoting a slave to a master in a single master, multiple slave environment (no replies)

$
0
0
Hi: I have 3 databases in a master and 2 slave setup. I would like to shutdown master and promote one of the slaves to be the master. I have reviewed multiple sites. Instructions vary slightly depending on when the document was created. Was hoping someone can review my steps and let me know if I am missing something.

I have mysql 5.7.22

1. Shutdown database M
2. On S1 and S2, run
 STOP SLAVE IO_THREAD;
3. SHOW PROCESSLIST on S1 and S2 should say "Slave has read all relay log; waiting for more update"
4. On S1
 STOP SLAVE; 
 RESET MASTER;
5. On S2
 STOP SLAVE; 
 CHANGE MASTER TO MASTER_HOST=S2' MASTER_USER=’slave’, MASTER_PASSWORD=......'; 
 RESET SLAVE; 
 START SLAVE;

Logging Skipped transaction in Replication (no replies)

$
0
0
Hi Team,

I want to --slave-skip-errors=[all] in my master and slave replication.
At the same time, I want to log faulty skipped Transitions to some log file so that they can be verified and taken appropriate action later on.

Is Slave relay log have these data? --log-slave-updates option will log all the statements executed by slave, I am looking for logging only skipped transitions.

Is there any way to do so? I am using MySQL 5.7 Row based GTID replication.

Regards,
Neelam

Mysql 8.0: server restart breaks replication (no replies)

$
0
0
Hello,

at least for me after migration new installations on 8.0 it really seems like server or mysql instance restart breaks the replication: after each restart I got duplicates on the primary keys, and looking at it's content I can see that it really looks like the slave SQl thread has inserted some of the binlog data but hasn't update the pointer to it, because these duplicates are exactly the same as they should be.

This behaviour is new in 8.0, as I run several 5.6/5.7 replication setups.
How can I get rid of these ? Right now I simply delete the duplicate data and start the slave threads all over.

Thanks.

AWS re:invent - Globalizing Player Accounts at Riot Games While Maintaining Availability (no replies)

$
0
0
The Player Accounts team at Riot Games needed to consolidate the player account infrastructure and provide a single, global accounts system for the League of Legends player base. To do this, they migrated hundreds of millions of player accounts into a consolidated, globally replicated composite database cluster in AWS. This provided higher fault tolerance and lower latency access to account data. In this talk, we discuss this effort to migrate eight disparate database clusters into AWS as a single composite database cluster replicated in four different AWS regions, provisioned with terraform, and managed and operated by Ansible.

Tyler Turk, Infrastructure Engineer, Riot Games

ARC314, Tuesday, Nov 27, 1:45 PM - 2:45 PM
– Aria East, Plaza Level, Orovada 2

https://www.portal.reinvent.awsevents.com/connect/sessionDetail.ww?SESSION_ID=22860&tclass=popup

Group Replication: coping with unreliable failure detection (no replies)

auto_increment_increment value for MySQL Group Replication on Single-Primary Mode (no replies)

$
0
0
Hello,

We are setting up this servers stack:

- 1x ProxySQL Server
- 2x MySQL Servers

We are using MySQL Group Replication between the 2 MySQL servers on "Single-Primary" Mode.

The default value for "auto_increment_increment" with this config is 7.

It's safe to set "auto_increment_increment" to 1 when using Single-Primary Mode?

Thanks!

MySQL 8.0: replication instrumentation: an insight on transaction retries (no replies)


MySQL Group Replication: instrumentation for memory used in XCom (no replies)

MySQL Shell: The DevOps Tool for MySQL (no replies)

MySQL 8.0: HA with InnoDB Cluster + Shell (no replies)

MySQL Replication: Temporary tables allowed in transactions with GTIDs (no replies)

Connect to Cloud and Local DB (1 reply)

$
0
0
Hi,

i'm totally new mysql so

i have app running in the cloud with mysql db, when the internet connection is lost than need to start the app on a raspberry pi incl. th mysql db but when the internet is back on i need to sync de local db to the cloud db.

1 DB cloud is master and need to sync local if internet is ok
2 when internet is lost need all data to go to local DB on rasp pi
3 When internet is back there need to be a sync from Local DB to Cloud DB

thanks for helping and sorry for may bad englisch

rgb

Database connections to Slave (1 reply)

$
0
0
Hi all,

am new to mysql. I have set up a master - slave setup.

My question is basic. does application /remote connections can happen in slave?

Like oracle , will there be a read-only option or slave cannot be used by application unless it is switched to master.

Channel based replication thread conflicts with Default Channel. (1 reply)

$
0
0
Hi All,

I am trying to set up a multi-channel replication with 2 Masters feeding one Slave.

If I manually start each channel using 'Start slave for channel 'slave1/2'; everything is fine.

But if the server reboots, or I just issue a normal "START SLAVE;' command, it seems like the original default channel still tries to launch. This then causes a conflict where either itself or one of the channel threads will error out.

SELECT * FROM replication_connection_status\G;
*************************** 1. row ***************************
CHANNEL_NAME:
GROUP_NAME:
SOURCE_UUID: 7382909c-e2ad-11e8-950f-000c2929361a
THREAD_ID: NULL
SERVICE_STATE: OFF
COUNT_RECEIVED_HEARTBEATS: 17
LAST_HEARTBEAT_TIMESTAMP: 2018-11-13 16:01:50.684358
RECEIVED_TRANSACTION_SET: 7382909c-e2ad-11e8-950f-000c2929361a:1-4
LAST_ERROR_NUMBER: 13114
LAST_ERROR_MESSAGE: Got fatal error 1236 from master when reading data from binary log: 'A slave with the same server_uuid/server_id as this slave has connected to the master; the first event '' at 4, the last event read from '/var/log/mysql/mysql-bin.000004' at 41461, the last byte read from '/var/log/mysql/mysql-bin.000004' at 41461.'
LAST_ERROR_TIMESTAMP: 2018-11-13 16:01:50.781611
LAST_QUEUED_TRANSACTION:
LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION:
QUEUEING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION_START_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000
*************************** 2. row ***************************
CHANNEL_NAME: sc-1
GROUP_NAME:
SOURCE_UUID: 7382909c-e2ad-11e8-950f-000c2929361a
THREAD_ID: 57
SERVICE_STATE: ON
COUNT_RECEIVED_HEARTBEATS: 5623
LAST_HEARTBEAT_TIMESTAMP: 2018-11-15 14:52:52.402809
RECEIVED_TRANSACTION_SET:
LAST_ERROR_NUMBER: 0
LAST_ERROR_MESSAGE:
LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION:
LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION:
QUEUEING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION_START_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000
*************************** 3. row ***************************
CHANNEL_NAME: sc-2
GROUP_NAME:
SOURCE_UUID: c5b263d8-e433-11e8-8c4f-5254009262e2
THREAD_ID: 59
SERVICE_STATE: ON
COUNT_RECEIVED_HEARTBEATS: 5623
LAST_HEARTBEAT_TIMESTAMP: 2018-11-15 14:52:51.955988
RECEIVED_TRANSACTION_SET:
LAST_ERROR_NUMBER: 0
LAST_ERROR_MESSAGE:
LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION:
LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION:
QUEUEING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION_START_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000
--------------------------

There is no Channel name, but the thread still tried to start and fails.

How can I remove or disable the default thread from running when the server reboots? Or is there another step I am missing here?

Thanks!

MySQL InnoDB Cluster with 2 Data Centers for Disaster Recovery: howto (no replies)

5.7.23 IO_THREAD stops with Heartbeat error (no replies)

$
0
0
MySQL Version: 5.7.23-community (from MySQL ppa)
OS: Ubuntu 16.04.3
Replication Type: Circular Multi-Master

This morning our replication was running fine. Then one of our master/slave servers' IO_THREAD just stopped working with the following error:

2018-11-26T16:45:31.993523Z 179530 [ERROR] Slave I/O for channel '': Unexpected master's heartbeat data: heartbeat is not compatible with local info; the event's data: log_file_name master-bin.0059625��� log_pos 651598942, Error_code: 1623
2018-11-26T16:45:31.993567Z 179530 [ERROR] Slave I/O for channel '': Relay log write failure: could not queue event from master, Error_code: 1595
2018-11-26T16:45:31.993577Z 179530 [Note] Slave I/O thread exiting for channel '', read up to log 'master-bin.005962', position 2281364567

I tried pointing the failing master/slave to other masters but keep getting the same error but with different logs name and position. Except for the number of processors and RAM, all the master servers are configured the same in the mysql.cnf file. I have tried restarting a master and the failing master/slave but it didn't help. I have also searched the internet for similar issues but I can't seem to find any relative info.

Any help regarding this error would be appreciative.

DB Replication Failover (no replies)

$
0
0
Hi All,

1. I have an application that writes 10 million of records per day. (We currently have one database - master that the application writes to it using its DNS record).
2. We want to implement replication (asynchronised).
3. I'd like to know what is the best method to do a failover with that method?What should be the order of things?
3.1 Do we switch to the new master and then change the DNS record to point to it? OR the opposite way?
3.2 Moreover - how can we switch back to the 'old' master once its restored?

Thank you.

--bind-address clarification (1 reply)

$
0
0
I am running MySQL 5.6 on Windows 2012 R2 Std. I have configured the server for multiple IPv4 address easily enough. I need to have an instance of MySQL associated with each IP on the same server. I have read up on the --bind-address parameter in the my.ini file but I am not sure I fully understand it. If I specify an IPv4 address in the bind-address parameter in the my.ini file does this mean any other server connecting to that specified ip and port will see that database or does that parameter specify that only that IP can connect to the server. I want multiple computers to be able to connect to a specific IP/port on my server that contains multiple IPs but that all connect to port 3306 associated with each IP.

e.g. If my server has an ip address of 10.10.2.48 and I am running mysql on port 3306. I want to have another IP on that same server I can also connect to 10.10.2.49 also on port 3306.

This is mainly so I can stack replication instances in case of massive failure and not have to physically duplicate each server. We are working towards virtualization but we are not there yet. I have an offsite backup location that I replicate to. I change the 3rd octet to differentiate the backup site and keep the 4th octet the same to easily identify which machines are which when we need to work from the backup site.

Replication table vs database (1 reply)

$
0
0
Hey Forum.
I'm testing at the moment a little test setup.

Ves01 - contains tt.12345_p
Ves02 - contains tt.98765_p

HQ1 - contains whole tt database - Replicate from ves01 & ves02 into one DB

HQ2 - contains whole tt database - Replicate from HQ1

My Replication works fine towards HQ1 - When trying to replicate from HQ1 to HQ2 - I'm getting OK and connection - reading the Master bin log.
But its not inserting any statement in HQ2

Starting the channel - gives me
Slave I/O thread for channel 'tt': connected to master 'mysql_replic@192.168.10.61:3306',replication started in log 'mysql-bin.000005' at position 4

Reads the whole bin log - but do not insert any rows.
In slave status I'm getting:
Slave_IO_State: Queueing master event to the relay log

Untill the binlog file have been read - no data is available. No errors getting.

Today I dump the whole DB from HQ1 - loaded into HQ2 - and startet replication again - but again the same result


What Am I doing wrong here
Viewing all 1562 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>