Sasha and Monty,
Nico had a problem in replication with InnoDB tables. Luckily
3.23.37 seems to solve his problems. But, meanwhile I was studying
'load table from master' and noticed that it uses a function
net_read_dump which is only defined for MyISAM tables.
The following printout is from 3.23.34 on Win NT, where I was able
to get replication working for InnoDB, but 'load table from master'
failed.
.....................
Innobase: Started
mysqld: ready for connections
010419 20:46:21 Slave thread initialized
010419 20:46:22 Slave: connected to master 'repl@localhost:3306', replication
started in log 'omnibook-bin.008' at position 432
010419 20:47:09 create_table_from_dump::failed in handler::net_read_dump()
010419 20:47:09 fetch_nx_table: failed on create table
......................
An obvious workaround is to alter an InnoDB table to MyISAM (in master),
do then 'load table from master' (in slave) and after that do ALTER TABLE
back to InnoDB in master. The slave will repeat the ALTER TABLE and the
end result is an InnoDB table which is identical on both systems.
Another workaround is to make a 'binary' backup of the InnoDB database,
as described in the InnoDB manual, of the master and copy the backup
then to the slave.
For 'load table from master' to work directly for InnoDB tables the MySQL
developer responsible for replication should program an alternate
method of transfer which uses SQL statements.
Regards,
Heikki
>Return-Path: <[EMAIL PROTECTED]>
>Sender: [EMAIL PROTECTED]
>Date: Thu, 19 Apr 2001 18:53:47 +0000
>From: Nicola Sabbi <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>X-Accept-Language: en
>To: Heikki Tuuri <[EMAIL PROTECTED]>
>Subject: Re: [Fwd: Replication non working with Innobase]
>References: <20010419143600.BZFW26396.fep06.tmt.tele.fi@omnibook>
>
>Hello,
>I solved all problems using 2.23.37 with redhat 7.0 + gcc-g++ and relative
libraries.
>
>Maybe it's a problem related to egcs*
>
>
>Thanks in advance.
>
>
>
>Heikki Tuuri wrote:
>
>> Nico,
>>
>> does the table you are trying to replicate contain rows
>> with more than 8000 bytes of data?
>>
>> InnoDB (= Innobase) cannot store longer rows. Arbitrary length BLOB and TEXT
>> fields are on the TODO list for June 2001.
>>
>> Does the slave hang also for other queries you try to do
>> on the slave's InnoDB tables?
>>
>> Regards,
>>
>> Heikki Tuuri
>> Innobase Oy
>>
>> >Hi,
>> >I'm using two Mysql 3.23.36 with Innobase tables on two machines running
>> >Redhat 7.0.I'm trying to use replication in a simple master/slave
>> configuration,
>> >but while it works
>> >when I use MyIsam tables, if one of the two machines tries to useInnobase
>> tables
>> >the replication doesn't work, both when they are configured to do itmanually
>> >and when I manually start the slave and launchload table news from master;
>> >in this last case after some seconds the slave complains of a network
>> >error (although the masteris alive and configured properly).
>> >Follows an excerpt from the log of the master,
>> >
>> >?func: general: Host: www2.MIOSITO.it ip: 193.207.81.207
>> >vio_keepalive: enter: sd=9, set_keep_alive=1vio_is_blocking: exit: 0
>> >>>>> vio_write: enter: sd=9, buf=0x82afad0, size=54 ***
>> >HERE IT WRITES SUCCESSFULLY 54 BYTES ON SOCKET 9>>>>vio_write: exit: 54
>> >>>>>vio_is_blocking: exit: 0>>>>vio_read: enter: sd=9, buf=0x82afad0, size=4
>> >*****HERE IT CAN'T READ 4 BYTES FROM THE SAME SOCKET
>> >>>>>vio_read: error: Got error 11 during read -1, 4294967295
>> >>>>>vio_read: exit: -1?func: info: vio_read returned -1, errno: 11
>> >thr_alarm: enter: thread: T@2051 sec: 5thr_alarm: info: reschedule
>> >vio_is_blocking: exit: 0
>> >
>> >So it seems the socket has been closed (maybe by the slave?).
>> >Does anyone have any suggestion?
>> >I'd also like to know if someone has Innobase replicating correctly, and
>> >if so what versions of c++ and libstdc++ he/she is using,
>> >I don't know if gcc is preferrable to egcs-g++.Thanks very much
>> >
>> > Nico
>>
>> ---------------------------------------------------------------------
>> Before posting, please check:
>> http://www.mysql.com/manual.php (the manual)
>> http://lists.mysql.com/ (the list archive)
>>
>> To request this thread, e-mail <[EMAIL PROTECTED]>
>> To unsubscribe, e-mail
<[EMAIL PROTECTED]>
>> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
