Continuent Community

Hi,

According to other posts I have read it seems that the sqlrouter and monitor configurations must be performed through the Tungsten Manager console. However I am not able to create / register datasources because when I enter the commit command I got a message that says the command do not exist.


[ADMIN] /cluster/moodle-cluster/> create cluster-master
[ADMIN] /cluster/testing-cluster/> commit
Unknown command: 'commit'


Also, is it necessary to copy the config files (that were created by the configure script in the cluster-home/conf directory) to the connector / sqlrouter config folders? (I did that because it seemed that the sqlrouter and connector applications were reading the files located in their own config directory)

The version of tungsten I am currently running is the 1.2.2

By the way, it seems that the wiki and enterprise documentation are outdated.

Thanks,

Dennis

Hi Dennis!
Data source creation is automatic with Tungsten. Just run the configuration script (./configure once you have unpacked the tungsten-community tarball) and enable only the components you need (for example, only the replicator).
Then, when you'll start the services on this host, the new data source will appear in other already running nodes.
Cheers,
Gilles.

Hi Gilles,

I have manually installed the replicator in the mysql servers (they are working OK). However I can not find a method to link those servers to the tungsten sqlrouter which is running on a dedicated server that will be used for the proxy / load-balancing task between the database servers and the web servers.

According to the manual I have to use the manager to add the datasources making use of the create datasource command; however the commit command is still failing.

Thanks,

Dennis

You need to run managers on all nodes, including replicators and routers + monitors on replicator nodes. How is your setup at the moment?
Once installed correctly, your new data sources should appear automagically. If not, make sure your managers can talk to each others using the "members" command in cctrl that will list, on each manager, the group members of the cluster
Hope these help
Cheers,
Gilles.

This is the setup at the moment in the testing environment:

Router node:
ip: a.b.c.d
node name: tungsten-proxy
tungsten services installed: sql-router, manager, connector
result of command members through the cctrl: testing-cluster/tungsten-proxy(ONLINE)/127.0.0.1:7800

Master node (This node has a mysql-server installed):
ip: a.b.c.e
node name: mysql-master
tungsten services installed: replicator, manager, monitor
result of command members through the cctrl: testing-cluster/mysql-master(ONLINE)/127.0.0.1:7800

Slave node (This node has a mysql-server installed):
ip: a.b.c.f
node name: mysql-slave
tungsten services installed: replicator, manager, monitor
result of command members through the cctrl: testing-cluster/mysql-slave(ONLINE)/127.0.0.1:7800

The replication is currently working.
However the router can not see the other nodes through the manager.

I was trying to add the datasources through the create datasource command; however the commit command is still failing.

Thanks,

Dennis

Hi Dennis,

It looks as if you might be running into some conceptual problmes about how Tungsten clusters work. In Tungsten you don't create data sources through cctrl. Instead, turning on services for a data source make it appear in the cluster the first time the data source goes online successfully.

Have you had a look at the full documentation for Tungsten clustering? We just posted a considerably updated version of the docs on www.continuent.com. Please check in particular the Tungsten Concepts and Administration Guide. It has a very full overview of the administration in particular and is a lot more helpful than the old version.

http://www.continuent.com/downloads/documentation

Please post any comments or suggestions back to the forums. Meanwhile, good luck with your cluster!

Cheers, Robert