Tag Info

New answers tagged

1

The solution appears to be presented to you multiple times in the log file you posted. Please use mysql_upgrade to fix this error. mysql_upgrade examines all tables in all databases for incompatibilities with the current version of MySQL Server. mysql_upgrade also upgrades the system tables so that you can take advantage of new privileges or ...


0

Enable the slow query log and log_queries_not_using_indexes on the slave server and should be able to confirm what your gut is telling you. You can take the captured queries, run EXPLAIN on them, and have some better documentation of your suspicions. To more directly answer the question, it's absolutely valid to declare indexes on a slave that are not ...


1

You may need to try something a little unorthodox service mysql stop Open mysql-bin.index in vi Change the contents to this ./mysql-bin.000313 ./mysql-bin.000314 ./mysql-bin.000315 Save mysql-bin.index service mysql start Login to MySQL and run SHOW BINARY LOGS; SHOW MASTER STATUS; This stunt worked a few times for me. Give it a Try !!!


0

Right click distributor job and change its schedule.


0

We have configured SQL 2008 R2 replication. Distributor is configured in continuous mode, publisher is scheduler is set to execute after every six hours. Now we want to change distributor schedule from continuous to schedule frequency without re-creating new replication. We have tried below store procedure, but it gives error message. Please help to ...


0

Take a look at your SQL Agent Jobs on the instance that hosts the subscriber database(s). Looking at Job Activity Monitor you should see them under the category named "REPL-Distribution"


0

Basically Advanced Replication works with materialized views, materialized view logs and triggers. To replicate data from one side to another, you need to have INSERT, UPDATE or DELETE statements to make the replication mechanism recognize that there is new/changed data. When you import data with direct path method you skip all this stuff. This means you ...


0

I don't have direct experience with a similar setup, but you probably need to set this option on the master services: --log-slave-updates Should slaves log updates to binlog [false] By default, changes made by appliers are not written to the binlog. As Tungsten watches the binlog to detect changes, the master extractor will not see those changes ...


0

We were able to resolve this using mysqldump instead of mydumper/myloader. Apparently there is a bug in myloader or in Galera itself which prevents replication to flow normally.


1

The Query Timeout message you are seeing is your Distribution Agent timing out, not your Log Reader Agent. You need to increase your Distribution Agent profile Query Timeout parameter value to alleviate the error. Please see the section To view and edit the parameters associated with a profile in Work with Replication Agent Profiles to edit the ...


0

Semisync Replication will switch to async on the fly if needed. I mentioned this before in my old post MySQL Replication : 1 Slave / Multiple Masters In that post I said Having this setup gives you block-level replication within both data centers. If you are using MySQL 5.5, you can have Semisynchronous Replication send SQL to the other DataCenter ...


0

I also recommend (as mentioned in first reply) to monitor data consistency across all servers binded to your master, becouse for variety of reasons sometimes replicas are not 100% copies. Some nice PHP script, that checks data integrity can be found here: https://github.com/KredytyChwilowki/MySQLReplicaIntegrityCheck It is an open source tool, very ...


0

For merge replication issues, first stop is to read Chris Skorlinski's blog post at http://blogs.msdn.com/b/repltalk/archive/2010/06/28/merge-replication-capacity-planning.aspx He links you to several resources at the top of his blog post. The post is from 2010, but merge replication has not had any significant update as far as I know. Chris's bottom line ...


1

you may need to grant super privileges to the user. Replication client is responsible only to replicate binary logs to slave


0

This is a typical network issue. If you check your logs all nodes lost connectivity with each other the same time which means that your network layer failed. Your configuration is fine , i would propose you to use DNS names instead of IPs which will make you more flexible.


1

If you are not writing directly on your slave, no binary logs will get generated by default. To capture the binary log events from the master into the slave's binary log, you need two things: enable log-bin enable log_slave_updates


0

You need to add the port to my.ini for the Master [mysqld] server-id=1 port=1000 log-bin=black-bin.log datadir=d:\mysql\master\ innodb_flush_log_at_trx_commit=1 sync_binlog=1 and restart mysql First run this STOP SLAVE; SHOW SLAVE STATUS\G From the output use Relay_Master_Log_File as CurrentLogFile use Exec_Master_Pos as CurrentLogPosition As ...


0

Replication filtering rules will only work on the situations where you do USE mysql; DROP TABLE failover_console; When you do DROP TABLE mysql.failover_console;, that will slip through the cracks. Why? The problem stems from you using Binlog_Ignore_DB: mysql. This looks for mysql to the the default database. Still, you explicitly use mysql. in front of ...


2

In general, actively writing to multiple masters in MySQL is a bad idea. MySQL Replication is asynchronous, which means there's no guarantee the changes make it to the slave before the changes are committed on the master. The implication is that something™ (node dies, slave lag, etc) can/will go wrong with one of the masters at any time. If your ...


0

From what I can tell it looks like it will usually transfer the whole file instead of using the delta-xfer algorithm unless you set the wsrep_sst_rsync_wan option. I assume this is because on a local network transferring the full file is close enough or as fast as calculating the deltas between the files. The relevant lines in the SST script for MariaDB ...


0

If the data is currently being updated on the replica, it could be due to a trigger (show triggers from [database];) or a replication rewrite flag (look at the my.cnf for master and slave).


1

Here are two possible setups you could try TOPOLOGY #1 Data Center #1 with two(2) DB Servers (DB1, DB2) Data Center #2 with two(2) DB Servers (DB3, DB4) Setup DRBD with Each Data Center Setup MySQL Replication Between the DRBD Primaries Setup DBVIP (Linux Heartbeat/ Pacemaker / ucarp) What this setup provides Synchronous Disk-Level Replication Within ...


3

There's three separate parts to this: Q: Do I use SQL Server's built-in log shipping or roll my own? A: I'd roll your own. What you're doing is beyond what the built-in tools are normally used for. Q: If I roll my own, where do I start? A: I'd use normal SQL Server full and transaction log backups on the primary. On the secondary, start with MSSQLTips' ...


0

If you've tried everything else then perhaps it would be possible (making sure you have a good backup first!) to detach the database, rename the log file (so SQL Server cannot find it) and then re-attach the database. I believe this will force SQL Server to create a new log file. Whether it will also stop thinking that the database is replicated I have no ...


0

I would also say it depends on the volume and what you want to do. Does your graph need to use real time data ? and does it use all data from these 6 databases ? In some situation a classic ETL (extract,transform,load) to a new database supporting heavy queries is the answer If you need quasi-real time data: Replicating heterogeneous databases is not easy, ...


0

I would try the following: USE <database_name_here> GO EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1 After which you could try adding a replication and removing a replication for an individual table in the database as suggested in post further down. We had a database at one time that switched to ...


1

It sounds like what you are looking for is an Always On Availability Group in Synchronous Commit mode with automatic failover. The transactions sync from the primary to the secondary and in the event of a system failure, will pass ownership of the database to the secondary. Your application would need to be aware of both the primary and secondary and which ...


0

Have you tried setting the database to not publish? use master exec sp_replicationdboption @dbname = N'<DATABASENAME>', @optname = N'publish', @value = N'false' GO and then backing up the log to see what happens? Edit 1 : What does the following t-sql return? -- Run on publisher database for Pub, subscriber information SET TRANSACTION ISOLATION ...


0

You can't configure a MySQL server to connect to multiple masters as a replication slave. You can configure Master B with log_slave_updates enabled, Master A with binlog_format = ROW and declare table 2 using Engine=BLACKHOLE on Master B, and the replication events from Master A's binary log will cascade through Master B onto Slave C, which would be ...


0

If your table is InnoDB format, then try pt-online-schema-change (from Percona Toolkit), for example: pt-online-schema-change --charset utf8 \ --alter 'ADD COLUMN baz INT UNSIGNED' \ --execute -h db-test -u username -p password D=foo,t=bar


1

Is it acceptable to have downtime on this database? This was probably either restored from a replicated database or it was possibly a subscriber that was improperly removed, though that is unlikely. You could try doing a backup from express and restoring to a standard or higher edition then setting up replication again and removing it. Then you can backup ...


0

You cannot see the conflict tables from within Replication Monitor. However, you can view the Conflict Viewer by right-clicking your Merge Publication in Object Explorer -> View Conflicts. Alternatively, you can directly query MSmerge_conflicts_info. For more information, see View and Resolve Data Conflicts for Merge Publication (SQL Server Management ...


0

This seems to be an age-old problem How To Repair MySQL Replication MySQL replication: "Houston, We've Got a Problem" ERROR Cannot find or open table? Some recommend skipping the error and continuing. Personally, you should handle stopping replication differently. Run STOP SLAVE;. This will freeze the IO Thread bytes ahead of the SQL ...


0

Right, it's modded. “We worked around this problem in fb-mysql by relaxing the constraint...” Note that fb-mysql is a link to https://github.com/facebook/mysql-5.6/ ... which is a Facebook fork branch of MySQL Server 5.6.


0

You might get away with using the eval ISO. Try download that, burn it to a disk (or mount it by other means) and see if it will cooperate. It'll certainly contain everything, assuming it is as happy to be used to update your licensed install as it is an eval one. EDit: I've removed the link as it was incorrect. It looks from trying to search on their site ...


1

As Antonis said, the number of connections has little relation to the number of databases. In general, the number of connections aren't something to worry about. The MongoDB drivers keep the connections alive to reuse them and to prevent the overhead of setting up new connections. However, each connection is provided with about 1MB of stack server side. ...


0

First of all you need to upgrade to 2.6.5 . The number of connections is not related to the number of databases. You probably run some bad queries or you perform heavy writes. Next step enable the profiler and examine slow queries and run a mongostat against the instance.


1

The filtered replication is not something that is currently implemented in MongoDB out of the box. That said, the replication in MongoDB is based on a special collection named "oplog", that you can listen to and do the filter yourself, and in this case implement the filter you want to push data into another cluster. (This will be viewed as 2 different ...



Top 50 recent answers are included