Re: [DRBD-user] the timing of restarting thread

2010-07-26 Thread Lars Ellenberg
On Mon, Jul 26, 2010 at 09:55:53PM +0900, Junko IKEDA wrote: > Hi, > > > If sockets fail in some detectable (by tcp) fashion, > > (RST, icmp unreachable or similar), > > both sockets are dropped. > > > > Replication is only reestablished once both sockets > > have successfully be reestablished. >

Re: [DRBD-user] the timing of restarting thread

2010-07-26 Thread Junko IKEDA
Hi, > If sockets fail in some detectable (by tcp) fashion, > (RST, icmp unreachable or similar), > both sockets are dropped. > > Replication is only reestablished once both sockets > have successfully be reestablished. > > If sockets fail in some "strange" way (no RST, no icmp, > just a black hole

Re: [DRBD-user] the timing of restarting thread

2010-07-25 Thread Lars Ellenberg
On Sun, Jul 25, 2010 at 01:38:56AM +0900, Junko IKEDA wrote: > Hi, > > >> > DRBD has _two_ tcp sessions per device, > >> > one end will have a "random high port", > >> > the end the configured port. > >> > >> Are these two sessions for "data" and "meta" socket as you mentioned below? > >> I think

Re: [DRBD-user] the timing of restarting thread

2010-07-24 Thread Junko IKEDA
Hi, >> > DRBD has _two_ tcp sessions per device, >> > one end will have a "random high port", >> > the end the configured port. >> >> Are these two sessions for "data" and "meta" socket as you mentioned below? >> I think I want to simulate the blocking of "meta" socket. > > Ah.  Why? > Please step

Re: [DRBD-user] the timing of restarting thread

2010-07-24 Thread Lars Ellenberg
On Sat, Jul 24, 2010 at 12:13:01AM +0900, Junko IKEDA wrote: > Hi, > > >> (1) start DRBD. > >>      node01 is "Primary" and node02 is "Secondary". > >> (2) block the replication port on node02. > >>      # iptables -A INPUT -i bond0 -p tcp --dport 7790 -j DROP > > > > insufficient. > > you have to

Re: [DRBD-user] the timing of restarting thread

2010-07-23 Thread Junko IKEDA
Hi, >> (1) start DRBD. >>      node01 is "Primary" and node02 is "Secondary". >> (2) block the replication port on node02. >>      # iptables -A INPUT -i bond0 -p tcp --dport 7790 -j DROP > > insufficient. > you have to block OUTPUT as well. Blocking both INPUT and OUTPUT goes to split brain, doe

Re: [DRBD-user] the timing of restarting thread

2010-07-23 Thread Lars Ellenberg
On Fri, Jul 23, 2010 at 06:15:05PM +0900, Junko IKEDA wrote: > Hi, > > I'm trying the following test. > > (1) start DRBD. > node01 is "Primary" and node02 is "Secondary". > (2) block the replication port on node02. > # iptables -A INPUT -i bond0 -p tcp --dport 7790 -j DROP insufficient

[DRBD-user] the timing of restarting thread

2010-07-23 Thread Junko IKEDA
Hi, I'm trying the following test. (1) start DRBD. node01 is "Primary" and node02 is "Secondary". (2) block the replication port on node02. # iptables -A INPUT -i bond0 -p tcp --dport 7790 -j DROP the result is; * protocol B,C DRBD did nothing. * protocol A It seems that DRBD restart