replication

问题 we are continuously getting this exception during replication from master to slave. our index size is 9.7 G and we are trying to replicate a slave from scratch. 30 Oct 2013 18:22:16,996 [explicit-fetchindex-cmd] ERROR ReplicationHandler - SnapPull failed :org.apache.solr.common.SolrException: Unable to download _41c_Lucene41_0.doc completely. Downloaded 0!=107464871 at org.apache.solr.handler.SnapPuller$DirectoryFileFetcher.cleanup(SnapPuller.java:1266) at org.apache.solr.handler.SnapPuller

问题 I've been experimenting with master-master replication between two MySQL servers but with different database names and I've come accross a bit of a stumbling block. It appears that although UPDATEs work correctly as expected, INSERTs do not. While I would say that this is a bug or at least a problem with my setup, it appears that MySQL says that this is a feature (here and here). If then, as MySQL say, it only works on the default database, then how can this setting have a practical real

问题 We have a merge replication topology including one publisher, multiple publications and multiple subscriptions. It has been running for at least 8 months without problems. A few days ago I was informed that my PO codes were being "changed" without any reasons, from a standard "ZWWTP/PO-0092" style to a new "ZWWT" style: characters 5 to 8 in the PO code were changed to another string being chr(0) & chr(1) & chr(0) & chr(1) on some servers I reached the point where it appeared that one only of

问题 SQL Server 2008R2 Transactional Replication - Move SubscriberDB - Push Subscription I have a requirement to move a subscriber database to a new server outside of a system outage i.e. I cannot stop new transaction from loading into the publisher database. So far I have attempted to stop the distribution agent and let all un-replicated commands replicate to the subscriber database at Server1. Then backup and restore the subscriber database to Server2. I have then created a new subscription from

问题 I'm trying to setup a push-from-server functionality based on PostgreSQL, pglogical and PostgreSQL's listen-notify mechanism. On my replicated table I've setup a trigger that uses pg_notify to push messages to queue after insert. Altered the trigger to "enable always trigger". With this setup, the behavior is not what I expected. After setting up a listen client (another postgresql console, also tried multiple python drivers, behavior is always the same), I don't get the notifications until I

问题 I have old database server as SQL Server 2000 whose data has to be periodically updated to the SQL Server 2008 server (may be one time per day). So I have planned to use the replication. First I have created distribution database in SQL Server 2000 & added the new database as publisher. But when I created the subscriber in SQL Server 2008 & connects to SQL Server 2000 then the publisher doesn't appear in the list. What could be the reason, I am using SQL Server 2008 express edition or if any

问题 curl http://usrname:password@192.168.1.10:5985/_active_tasks shows the following. In particular checkpointed_source_seq": 0. So my replication apparently isn't getting done. Is that due to a lack of response from the source server (iriscouch.org)? I'm not sure if it matters, but I'm also curious to know where the replication "logic" is happening, on the target or the source. (I restarted my couchdb and the checkpointed_source_seq is still 0, but docs_read, docs_written, missing_revisions

问题 I need to set up real time sync process between a on premise postgresql instance with cloud postgresql instance. Please let me know what are all the options available through which i can achieve it. Do i have to use any specific tool or it can be managed through replication . Please advice 回答1: Use PgPool http://www.pgpool.net/mediawiki/index.php/Main_Page from their web page: pgpool-II can manage multiple PostgreSQL servers. Using the replication function enables creating a realtime backup

问题 I was doing a streaming replication between 3 nodes of postgresql-9.5 . 1 master and 2 slaves I was trying to configure auto failover but when i switched back to my original master, and restarted the postgres service, I am getting the following error:- highest timeline 1 of the primary is behind recovery timeline 11 Can somebody please help. Thanx in advance 回答1: I'm not sure what you exactly mean by "when i switched back to my original master", but it looks that you are doing the wrongest

问题 I have created a trigger that works like this: After deleting data from table flux_tresorerie_historique it insert this row in the table flux_tresorerie_historique that is located in another database archive I use dblink to insert data in the remote database, the problem is that the creation of the query is too hard especially that the table contain more than 20 columns, and I want to create similar functions for 10 other tables. Is there another rapid way to ensure this task? Here an example