Hi Robert!
I checked the logs but your first assumption was right. I copy the files
mysqldump, mysqladmin and mysql to the bin directory of the SEQUOIA_HOME
and it worked perfectly! So thanks very much. I have the last question
and i promise is the last time i waste your time.
I am doing load balancing between 2 tomcat servers in different
computers (just clarify). In each of them i have a sequoia controller
with a virtual database
containing two MySQL Server (each of them in each computer). Each tomcat
is accessing only to its controller, that means that the code of the
Servlet is
"jdbc:sequoia://localhost/test;user=test;password=test". Do u think is
this a good configuration?
Is it better if i use both controller in the connection string, like
"jdbc:sequoia://server1,server2/test;user=test;password=test"????
Do i need to change something in my RecoveryLog configuration like using
the sequoia address instead the direct one to the MySQL Server??? In
that case
which backuper should I use????
Sorry but i didnt get this point in the UserGuide. Anyway THANKS VERY
MUCH for everything!!!!!!!!!!!!!!!
Robert Hodges escribió:
Hi Diego,
What do you see if you look in the full_cluster.log? There's usually a
pretty clear error message. Here are some possibilities:
1.) mysqldump is in *your* path but not in the path of the controller
process. This should be indicated by the log message.
2.) mysqldump version is not compatible with your particular MySQL instance.
I would look in the log to find the exact command that was run and try to
run it directly off the command line. When it works properly you are set to
go.
3.) Other problem. Look at the log message.
BTW, when scanning the log there's a pretty big stack trace. (Sorry, I was
actually responsible for the messy output.) Ignore that and search for
'mysqldump'.
Cheers, Robert
On 3/4/08 9:50 AM, "Diego" <[EMAIL PROTECTED]> wrote:
Hi,
thanks for the input... things are getting better. I changed my conf
file so the tables are properly created. I have two MySQL server nodes.
What i am doing is what is suggested in UserGuide. MySQL Server version
is 5.0.51a.
From sequoia console i am running...
initialize mysql-node1
backup mysql-node1 my_initial_dump Backuper backups
CreateProcess: mysqldump --version error=2
I am getting this error. At the beginning i thought it was cause of the
PATH so i changed the PATH so mysqldump is in PATH, but unfortunately
nothing changed... so do anyone help me with this?
Thanks u all very much in advance and thanks Emmanuel for the last quick
response.
################ Config File ####################################
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE SEQUOIA PUBLIC "-//Continuent//DTD SEQUOIA 2.10.9//EN"
"file://C:/sequoia-2.10.9-bin/xml/sequoia.dtd">
<SEQUOIA>
<VirtualDatabase name="test">
<Backup>
<Backuper backuperName="Sleepy"
className="org.continuent.sequoia.controller.backup.backupers.MySQLBackuper"/>
</Backup>
<AuthenticationManager>
<Admin>
<User username="root" password="sequoia"/>
</Admin>
<VirtualUsers>
<VirtualLogin vLogin="test" vPassword="test"/>
</VirtualUsers>
</AuthenticationManager>
<DatabaseBackend name="mysql-node1"
driver="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost/demo"
connectionTestStatement="select 1">
<DatabaseSchema dynamicPrecision="table"/>
<ConnectionManager vLogin="test" rLogin="root"
rPassword="novatia.djp">
<VariablePoolConnectionManager initPoolSize="20"
minPoolSize="5" maxPoolSize="0" idleTimeout="180" waitTimeout="0"/>
</ConnectionManager>
</DatabaseBackend>
<DatabaseBackend name="mysql-node2"
driver="com.mysql.jdbc.Driver" url="jdbc:mysql://192.168.1.18/demo"
connectionTestStatement="select 1">
<DatabaseSchema dynamicPrecision="table"/>
<ConnectionManager vLogin="test" rLogin="root"
rPassword="novatia.djp">
<VariablePoolConnectionManager initPoolSize="20"
minPoolSize="5" maxPoolSize="0" idleTimeout="180" waitTimeout="0"/>
</ConnectionManager>
</DatabaseBackend>
<RequestManager>
<RequestScheduler>
<RAIDb-1Scheduler level="passThrough"/>
</RequestScheduler>
<RequestCache>
<MetadataCache/>
<ParsingCache/>
<ResultCache granularity="table" />
</RequestCache>
<LoadBalancer>
<RAIDb-1>
<WaitForCompletion policy="first"/>
<RAIDb-1-LeastPendingRequestsFirst/>
</RAIDb-1>
</LoadBalancer>
<RecoveryLog driver="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost/demo" login="root" password="novatia.djp">
<RecoveryLogTable tableName="logtable"
vloginColumnType="TEXT NOT NULL"
sqlColumnName="sqlcol"
sqlColumnType="TEXT NOT NULL"
sqlParamColumnType="TEXT"/>
<CheckpointTable tableName="checkpointtable"
checkpointNameColumnType="TEXT NOT NULL"
extraStatementDefinition=",PRIMARY KEY (name(767))"/>
<BackendTable tableName="backendtable"
databaseNameColumnType="TEXT NOT NULL"
backendNameColumnType="TEXT NOT NULL"
checkpointNameColumnType="TEXT NOT NULL"/>
<DumpTable tableName="dumptable"
dumpNameColumnType="TEXT NOT NULL"
dumpPathColumnType="TEXT NOT NULL"
dumpFormatColumnType="TEXT NOT NULL"
checkpointNameColumnType="TEXT NOT NULL"
backendNameColumnType="TEXT NOT NULL"
tablesColumnType="TEXT NOT NULL"/>
</RecoveryLog>
</RequestManager>
</VirtualDatabase>
</SEQUOIA>
Emmanuel Cecchet escribió:
Diego,
- adding in the xml virtual database setup file:
<Backup>
<Backuper backuperName="Octopus"
className="org.continuent.sequoia.controller.backup.backupers.OctopusBackupe
r"/>
</Backup>
For MySQL you should use the MySQLBackuper instead, Octopus is only
for databases that are not supported by a specific backuper.
- and setting up the RecoveryLog like:
<RecoveryLog driver="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost/demo" login="root"
password="*******"> <RecoveryLogTable
tableName="logtable"
sqlColumnName="sqlcol"/>
<CheckpointTable tableName="checkpointtable"/>
<BackendTable
tableName="backendtable"/>
<DumpTable tableName="dumptable"/>
</RecoveryLog>
- The tables were created manually as specified in the userGuide
except for the column sql which i changed. And i am using
VARCHAR(255) for those columns
which are specified as VARCHAR.
The Sequoia controller creates the tables automatically, you don't
need to create these tables manually.
VARCHAR(255) is likely to be too small to store SQL. In MySQL post
5.0.3, VARCHAR should store 64K
(http://dev.mysql.com/doc/refman/5.0/en/char.html). If your SQL
statements can be larger, use TEXT instead (see
http://dev.mysql.com/doc/refman/5.0/en/blob.html for the limitations).
Hope this helps,
Emmanuel
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
