Re: Fw: Replication

Hello,

So, you are saying that the fact that replication is
not working when we re-connect is not a bug.

Replication is all about passing data from one node
(a master) to the next (the slave).  I do not know what
it is you want.  Simply when we re-connect we expect
it to replicate.

what you did (took the slave off line by pulling the RJ45),
what you wanted to happen (replication to occur),
and what actually happened (nothing - it did not replicate)

I am not look for support on how to set it up.

This is a bug.  I should be able to turn-off a slave
and when it comes back up have it replicate with its
master - correct?

Sorry, I do not know why we are having a problem. I
am simply stating the problem - if you need more, You
need to tell what you need.

Sam

----- Original Message -----
From: "Alexander Keremidarski" <[email protected]>
To: "sam [email protected]" <[email protected]>
Cc: <[email protected]>
Sent: Friday, August 22, 2003 6:15 PM
Subject: Re: Fw: Replication


> Hello,
>
> sam [email protected] wrote:
> > Thanks for the response.
> >
> > In the email, I stated "the setup" and "what caused the problem".
> > So, to repeat the problem setup replication with three nodes
> > and pull the RJ45 on one of them, update a record, then reconnect.
> > I used 4.0.13-nt version on all three nodes.
> >
> > We did this may times and pulled the RJ45 using a different node
> > each time.
>
> Sorry to say it that way, but you don't leave me much choices.
>
> This list is dedicated for Bugs only. Bugs with repeateable test cases
which we
> can use to check the problem.
>
>  > Please ask specific question if this is not enough.
>
> Bugs list is not intended to provide any kind of Support.
>
> You may ask for support for free at general list [email protected] or
you may
> consider using Support and Consulting services of MySQL AB as described at
> http://www.mysql.com/support/
>
>
> If you want someone to help you with troubleshooting your MySQL setup this
is not
> right list to write to.
>
>
> So if you believe you have hit a bug send us detailed instructions what
exactly
> happens, how to repeat it and test it.
>
> Refer to "How to Report a Bug" page at our Bugs Database site
> http://bugs.mysql.com/how-to-report.php
>
>
>  > Statements like this do not help: "No matter what kind of problem you
>  > describe "does not work" is never enough."
>
>  From what you have sent so far it is not clear what the problem is. The
most
> specific thing you said
>
> " When I re-connect n3 replication does not work. "
>
> This can mean wide range of things - from "a table at n3 does not contain
expected
> data" to "mysqld n3 crashed and corrupted tables"
>
>
>
> Quoting our "How to Report a Bug" page:
>
> <quote>
>
> The basics: what you did, what you wanted to happen, and what actually
happened.
>
> Those are the three basic elements of a bug report. You need to tell us
exactly
> what you did (for example, "My program runs the query SELECT * FROM
happy_meals
> WHERE sandwich = 'hamburger' AND side = 'onion rings'), what you expected
to have
> happen (to continue the example, "I expected MySQL to return a happy meal
with a
> hamburger and onion rings"), and what actually happened ("It gave me a
happy meal
> with french fries.").
>
> Yes, the example is silly. But if your bug report simply said "Querying
the
> happy_meals table doesn't work," we wouldn't be able to say "That's
because you
> can't have onion rings in a happy meal, you can only have french fries or
curly
> fries." By telling us what you asked for, what you expected to get, and
what you
> actually got, we don't have to guess.
>
> <end of quote>
>
> > Sam
>
> Best regards
>
> --
>   Are you MySQL certified? -> http://www.mysql.com/certification
>   For technical support contracts, visit https://order.mysql.com/?ref=msal
>      __  ___     ___ ____  __
>     /  |/  /_ __/ __/ __ \/ /    Mr. Alexander Keremidarski
<[email protected]>
>    / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Full-Time Developer
>   /_/  /_/\_, /___/\___\_\___/   Sofia, Bulgaria
>           <___/  www.mysql.com
>
>
>
>
> --
> MySQL Bugs Mailing List
> For list archives: http://lists.mysql.com/bugs
> To unsubscribe:    http://lists.mysql.com/[email protected]
>
>


-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]