MASTER / SLAVE REPLICATION
In Master/Slave Replication, you should not have any output from SHOW SLAVE STATUS\G on the Master. If you see any output, it is more than likely stale and no longer needed. You can remove that with the following commands
RESET SLAVE ALL;
After running these commands on the Master, you should get this from SHOW SLAVE ...
I don't think there is a "best practice" for archiving chunks of the data.
Some points to ponder:
Are you limited in disk space? On the Primary server? On the Replica? If yes to both, then some form of compression would be a temporary solution. Or, as you suggest, moving chunks to a 3rd server.
Will you need to restore the archived data? ...
Answer is yes! One physical server can act as an arbiter for two different replica sets, WHEN those arbiters are in different ports.
So, you will start two arbiters with two different config-files and data-directories.
How you will do it (I mean start those processes), it's your own choice. You can have two systemd etries (with different values) or you have ...
Depends, what you mean by "server". One machine/host - then answer is YES. If you mean the mongod process then answer is NO.
Each Replica Set needs to have a dedicated Arbiter instance. But it is no problem to create several Arbiter mongod services on one machine, just ensure different replSetName and different ports. There service names must ...
How does Transactional Replication relate to Availability Groups? Does
Availability Groups use Transactional Replication under the hood or
are they separate features? Can I use Transactional Replication
without Availability Groups?
Transactional replication doesn't relate to Availability Groups, other than the fact that they're both SQL Server technologies. ...
First thing I'll mention is, while it's allowable, it's not recommended to make changes to the Tables at the Subscription database, including data changes, unless you're using Updatable Subscriptions.
Secondly, the dropping of the tables only happens when you initialize the Subscriber, which should only occur on the initial creation, and whenever you add ...
SQL Server Express supports Merge Replciation where changes made at subscribers are synchronized to the publisher and then out to other subscribers in a hub-and-spoke topology. The "hub" instance is the only "publisher" and would need to be SQL Server Standard Edition or higher.
The other option is to turn on Change Tracking and write ...
First of all, this is not an error, just a "note". If it were an actual error, it would say 'error'.
The meaning of the message: An attempt at connecting from this host to one of the two other hosts in the cluster timed out - and the timeout is set to 3 seconds.
However, as per the subsequent messages, it then tried connecting again, and thankfully ...
I saw in some installations home-written SQL scripts that mimic SQL transaction log shipping. If you google, you will get plethora of resources. I.e. how to achieve t-log shipping with T-SQL scripts. For example: LINK
It all boils down to backing up your SOURCE server to shared folder where your TARGET servers have access and the TARGET servers restore these ...
This is a duplicate of RDS Postgres oldest replication lag increases during inactivity even though Fivetran connector keeps synchronizing
Due to a lack of writes at the source, there's nothing to sync and (for whatever reason) postgresql retains write ahead logs in this case - until there is something to sync.
Doing an INSERT at the source caused ...
Apparently this is possible.
From Microsoft support:
"XA is supported as this is depends on the storage engine (Innodb which supports the XA) , and the client driver/connector to understand the XA SQL statements and the customer application through the transaction manager should manage these things , and also recently we added to Azure database for ...
TLDR; It was a different password for 'repl'@'localhost' and 'repl'@'xx.xxx.xx.xx'.
So while rebuilding the slave node, I had updated the password for 'repl'@'xx.xxx.xx.xx', but did not update the password for 'repl'@'localhost'.
The pacemaker resource mysql was using the old replication_passwd, which was the reason why every time the slave node would ...
I was using Server B as its own distributor, and it was a pull subscription hence the above method did not work. I then deleted the existing replication and set it up as per link suggested by J.D.( push replication) and it worked like a dream.
In my case setting global variable innodb_flush_log_at_trx_commit = 2 on the replica server made a huge difference. Things to keep in mind:
from mysql docs (https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_flush_log_at_trx_commit)
With a setting of 2, logs are written after each transaction commit and flushed to disk once per ...
Yes this is possible, and most types of Replication should allow you to accomplish this, but since you said you only need it to synchronize in one direction then Transactional Replication is probably the most ideal solution. It's also typically the most flexible type of Replication, especially since it supports heterogenous Publishers:
The problem is that for security reasons, the search_path is set empty during replication replay. So you have to qualify the object names with the schema in the trigger function, for example public.mtable_history.
max_connections = 100 -> 3000 -- probably excessive
innodb_io_capacity = 400 -> 4000 -- probably excessive for HDD
thread_stack = 128K -- Let the default stand; it depends on the OS
wsrep_slave_threads=0 -- sounds wrong
gcache.page_size=1G -- Do you have a rationale for this non-default value?
Run SHOW GLOBAL STATUS ...