Hello, Just to followup up: this is not connectivity issue, but rather specific database to database replication. So, basically when I trigger a replication from A to B, it would pick up from the same sequence it got stuck on last time and then fail. Then if we stop it and start again the same thing happens. So the question is: how does one fully clear the replication state from one db to another, so I can start replication from A to B from scratch?
On Mon, Aug 25, 2014 at 11:36 AM, Andrey Kuprianov < [email protected]> wrote: > Hi guys, > > We are having this replication problem on a couple of our servers. Here's > a Gist with the log (https://gist.github.com/andreyvk/62f788075fe42acf4720). > I had to star some sensitive data. > > Servers are pulling data from each other and each of them is also pulling > from one more server. The whole setup was working very well until recently. > > The error log contains a lot of stuff which i dont know how to interpret. > I can see some request timeout messages between the lines and hopefully > that what's happening right now, but I cannot be sure because I can freely > ssh between the servers (hence, connectivity is good). > > Also, when replication is started, Futon shows "Checkpointed source > sequence 2677194, current source sequence 2694398, progress 100%", which > cant be true. Moreover, checkpointed sequence is stuck on the same number > and is not changing. > > Did anyone experience similar problem? > > Andrey >
