|
TungstenReplicatorIntro
Introduction to Tungsten Replicator
Featured IntroductionTungsten Replicator is an open source high performance replication engine that can replace MySQL native replication and greatly enhance the user experience with a broader feature set. OverviewTungsten Replicator is not integrated into MySQL. It is, in fact, written in Java, and it is thus totally external to the database server. The little inconvenience of this non-integration is more than compensated by the set of features that the replicator offers. MySQL native replication is a simple pipeline of data from one master to one or more slaves. This simple paradigm makes MySQL replication easy to deploy and administer, but it also results in a lack of features and functionality. Most of what MySQL native replication cannot do, Tungsten Replicator can achieve easily with its dynamic architecture. Just to mention a few issues, Tungsten Replicator implements Global Transaction IDs, which make master seamless failover an easy task. MySQL masters know little or nothing about its slaves, and the slaves themselves have no visibility of the other nodes. Tungsten replicator allows the DBA to see the replication cluster as a whole, rather than as a collection of servers. Operations like master switch can be performed from any node, and quite easily. More notable features are:
|
► Sign in to add a comment
Hi
I am kindly asking that you please send me a step by step tutorial on how to set up fan in replication with two separate databases on two master servers being replicated onto one shared database on a slave machine using tungsten replicator. It is my first time to use tungsten so I need a detailed approach right from installation to configuration and lastly testing.
I have searched the internet and all I can find is the fact that it is possible but not how exactly to do so.
Your assistance will be greatly appreciated.
Rumbi mukrue@yahoo.com
What steps will reproduce the problem?
I am following this tutorial on seting up fan-in or multi-source replication: http://datacharmer.blogspot.com/2011/08/usability-improvements-in-tungsten-204.html The main problem is in setting the datasource in this step --datasource=qa_r4_continuent_com
I know that the datasource is different from the database name, but how do I view it for the mysql database I am using. Was it automatically created, since research tells me that it is used when executing queries on a database. If so, how do I view the datasource in ubuntu?
If it is not automatically created, how do I set it or how do I create it? Could you please post a step by step tutorial or provide a reliable link to a tutorial that shows me how to resolve this problem.
Rumbi
What is the expected output?
...
What do you see instead? ERROR >> localhost >> You must specify a datasource alias or datasource confi ERROR >> localhost >> There was a problem parsing the arguments ERROR >> localhost >> You must specify a datasource alias or datasource confi ERROR >> localhost >> There was a problem parsing the arguments
tungsten-replicator/bin# $TUNGSTEN_BASE/tungsten/tungsten-replicator/bin/trepctl status pendingExceptionMessage: Client handshake failure: Client response validation failed: Client requested non-existent transaction: client source ID=localhost seqno=86 client epoch number=65
...
What version of the product are you using... tungsten-replicator-2.0.4 Binary Build
On what operating system? turnkey 32-bit ubuntu virtual machine ...
Rumbi