Fw: Replication

------=_NextPart_000_00A1_01C368C1.658074C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Here is the setup.

Ring architecture. I setup three machine.

Node Master Salve
1 n3 n2
2 n1 n3=20
3 n2 n1


If I pull the RJ45 from the nic on node 3. If I update a record on n1
it replicates to n2. When I re-connect n3 replication does not work.


sam

------=_NextPart_000_00A1_01C368C1.658074C0--

Re: Fw: Replication

Hello,

spizzuto wrote:
> Here is the setup.
>
> Ring architecture. I setup three machine.
>
> Node Master Salve
> 1 n3 n2
> 2 n1 n3
> 3 n2 n1
>
>
> If I pull the RJ45 from the nic on node 3. If I update a record on n1
> it replicates to n2. When I re-connect n3 replication does not work.

Please provide repeatable test case.
No matter what kind of problem you describe "does not work" is never enough.

> 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
/ /|_/ / // /\ \/ /_/ / /__ 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/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: Fw: Replication

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.

Please ask specific question if this is not enough.

Statements like this do not help: "No matter what kind of problem you
describe "does not work" is never enough."

Sam

----- Original Message -----
From: "Alexander Keremidarski"
To: "spizzuto"
Cc:
Sent: Friday, August 22, 2003 4:19 PM
Subject: Re: Fw: Replication


> Hello,
>
> spizzuto wrote:
> > Here is the setup.
> >
> > Ring architecture. I setup three machine.
> >
> > Node Master Salve
> > 1 n3 n2
> > 2 n1 n3
> > 3 n2 n1
> >
> >
> > If I pull the RJ45 from the nic on node 3. If I update a record on n1
> > it replicates to n2. When I re-connect n3 replication does not work.
>
> Please provide repeatable test case.
> No matter what kind of problem you describe "does not work" is never
enough.
>
> > 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

> / /|_/ / // /\ \/ /_/ / /__ 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/bugs?unsub=sam@esamiam.com
>
>


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: Fw: Replication

Hello,

sam samuel.pizzuto@esamiam.com 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 mysql@lists.mysql.com 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:



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.



> 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
/ /|_/ / // /\ \/ /_/ / /__ 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/bugs?unsub=gcdmb-bugs@m.gmane.org

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"
To: "sam samuel.pizzuto@esamiam.com"
Cc:
Sent: Friday, August 22, 2003 6:15 PM
Subject: Re: Fw: Replication


> Hello,
>
> sam samuel.pizzuto@esamiam.com 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 mysql@lists.mysql.com 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:
>
>
>
> 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.
>
>
>
> > 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

> / /|_/ / // /\ \/ /_/ / /__ 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/bugs?unsub=sam@esamiam.com
>
>


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: Fw: Replication

Sam,

On Fri, Aug 22, 2003 at 08:37:33PM -0400, sam samuel.pizzuto@esamiam.com wrote:
> 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.
>

See the section in the manual about replication features and problems:

If connection to the master is lost, the slave will retry immediately,
and then in case of failure every master-connect-retry (default 60)
seconds. Because of this, it is safe to shut down the master, and then
restart it after a while. The slave will also be able to deal with
network connectivity outages. However, the slave will notice the network
outage only after receiving no data from the master for slave_net_timeout
seconds. So if your outages are short, you may want to decrease
slave_net_timeout ; see section 4.5.7.4 SHOW VARIABLES.

http://www.mysql.com/documentation/mysql/bychapter/manual_My SQL_Database_Administration.html#Replication_Features


Regards,

Fred.

--
Fred van Engen XB Networks B.V.
email: fred.van.engen@xbn.nl Televisieweg 2
tel: +31 36 5462400 1322 AC Almere
fax: +31 36 5462424 The Netherlands

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org

Re: Fw: Replication

Hello,

sam samuel.pizzuto@esamiam.com wrote:
> Hello,
>
> So, you are saying that the fact that replication is
> not working when we re-connect is not a bug.

No I did not tell anythign like this. I told you you did not provided us with
enough details.

> 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.

Repeatable test case. Like:
Run 4.0.14 Master with following my.cnf and Slave 4.0.14 with following my.cnf
both on OS XYZ, then after Replication is working drop and restore network
connection and you will see following Error in SHOW SLAVE STATUS

> 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)

Sorry, but sentence above still says NOTHING. What exactly do you mean by
"Notihing - it did not replicate"

It was so easy to provide us with any output which can demonstrate the fact that
"it did not replicate"

Compare your emails with reports in Bugs Database. Like for example this one
related to Replication http://bugs.mysql.com/bug.php?id=1014 or this one which is
not Replication related, but is perfect example of well written bug report.

> 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?

I agree with you. If you guide us how to repeat the problem and if it happens with
latest releases of MySQL yes it is bug we will fix. Before that we can't do
anything about it because there are thousands of users using Replication without
experienced such problem.

> 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.

I told you. All we need is Repeatable Test Case.

Right now I have working replication over cable modem line which goes on and of at
least 4 times in a week. This never breaks replication. This does not "prove"
anything. I don't say there is no bug. All I'm saying I don't know how to repeat
your problem and you don't provide enough information. Not even MySQL version.
I simply don't understand your attitude.

>
> 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
/ /|_/ / // /\ \/ /_/ / /__ 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/bugs?unsub=gcdmb-bugs@m.gmane.org