List:General Discussion« Previous MessageNext Message »
From:Kishore Jalleda Date:February 8 2006 4:52pm
Subject:Re: 5.0.18-max-log as a slave of a 4.1.13-standard-log master problem - slave hangs
View as plain text  
Could you post the error log entries from the slave and the binlog where the
slave hangs , also just to make sure d2 and d3 replicate well without any
problems from d1 right ? also as per your message  d4 and d5 would work well
if no replication is enabled at all so essentially its only the replication
that is causing the hang right?????( could you clarify this for us ) ,

finally if thats the case and you feel that you have no error on your side (
assuming you have exhausted all the possibilities trying to isloate the
problem) but still the slave hangs, then you might want to open up a bug
report  http://dev.mysql.com/doc/refman/5.0/en/replication-bugs.html

hope this helps .....
Kishore Jalleda






On 2/8/06, Jan Kirchhoff <kirchy@stripped> wrote:
>
> Kishore Jalleda schrieb:
> > Hi you may be having issues with the byte order on the opetron's and the
> > P4's , this was asked earlier in the list, and here's what Jimmy from
> Mysql
> > had to say ............
> Kishore,
> Thanks for the suggestion, but all x86 have the same byte order... and
> as I wrote its not a cluster problem but a replication problem :(
>
> btw: I just started the mysql-tests and it hangs, too:
>
> db5:/usr/local/mysql/mysql-test# ./mysql-test-run
> Installing Test Databases
> Removing Stale Files
> Installing Master Databases
> running  ../bin/mysqld --no-defaults --bootstrap --skip-grant-tables
> --basedir=.. --datadir=mysql-test/var/master-da
> ta --skip-innodb --skip-ndbcluster --skip-bdb
> Installing Master Databases 1
> running  ../bin/mysqld --no-defaults --bootstrap --skip-grant-tables
> --basedir=.. --datadir=mysql-test/var/master-da
> ta1 --skip-innodb --skip-ndbcluster --skip-bdb
> Installing Slave Databases
> running  ../bin/mysqld --no-defaults --bootstrap --skip-grant-tables
> --basedir=.. --datadir=mysql-test/var/slave-dat
> a --skip-innodb --skip-ndbcluster --skip-bdb
> Manager disabled, skipping manager start.
> Starting ndbcluster
> Starting ndbd
> Starting ndbd
> Waiting for started...
> NDBT_ProgramExit: 0 - OK
> Connected to Management Server at: localhost:9350
> Cluster Configuration
> ---------------------
> [ndbd(NDB)]     2 node(s)
> id=1    @127.0.0.1  (Version: 5.0.18, Nodegroup: 0, Master)
> id=2    @127.0.0.1  (Version: 5.0.18, Nodegroup: 0)
>
> [ndb_mgmd(MGM)] 1 node(s)
> id=3    @127.0.0.1  (Version: 5.0.18)
>
> [mysqld(API)]   4 node(s)
> id=4 (not connected, accepting connect from any host)
> id=5 (not connected, accepting connect from any host)
> id=6 (not connected, accepting connect from any host)
> id=7 (not connected, accepting connect from any host)
>
> Loading Standard Test Databases
> Starting Tests
>
> TEST                            RESULT
> -------------------------------------------------------
> alias                          [ pass ]
> alter_table                    [ pass ]
> analyse                        [ pass ]
> analyze                        [ pass ]
> ansi                           [ pass ]
> archive                        [ pass ]
> archive_gis                    [ pass ]
>
> <now nothing happens, cpuload is at 0 - any ideas?>
>
>
> Jan
>

Thread
5.0.18-max-log as a slave of a 4.1.13-standard-log master problem- slave hangsJan Kirchhoff31 Jan
  • Re: 5.0.18-max-log as a slave of a 4.1.13-standard-log master problem- slave hangsJan Kirchhoff1 Feb
    • Re: 5.0.18-max-log as a slave of a 4.1.13-standard-log master problem- slave hangsJan Kirchhoff7 Feb
      • Re: 5.0.18-max-log as a slave of a 4.1.13-standard-log master problem - slave hangsKishore Jalleda7 Feb
        • Re: 5.0.18-max-log as a slave of a 4.1.13-standard-log master problem- slave hangsJan Kirchhoff8 Feb
          • Re: 5.0.18-max-log as a slave of a 4.1.13-standard-log master problem - slave hangsKishore Jalleda8 Feb