Mon Jul 16 04:50:46 PDT 2007
- Previous message: [Slony1-general] Log Shipping with slony.
- Next message: [Slony1-general] Trouble with large DB and windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I have thought about firewalls and timeouts. I just have two machines, sitting next to each other connected by a switch. One has Vista, the other XP. I tried running the slon engines on either one. I also tried changing all of the IP settings available. I also tried adding a linux machine and running the slon process on that machine. In every case, the machine that is the slave failed after about 12 - 15 GB with a error 10055 (not enough buffer space or enough tcp buffers). Also, the database I am trying to replicate is very simple. One table, no indexes. Even the table is simple. On serial column as primary key, the other is bytea data. Any suggestions? Al >> What I still can not do is replicate a 22 GB database. My initial >> trials all failed after about 12 to 15 GB with an error 10055 in >> the logs. According to windows knowlegebase, this is because of a >> lack of TCP buffers. I followed microsoft's advice and edited the >> registry and changed such things as the MaxUserPort and >> TCPTimedWaitDelay and TcpNumConnections to their maximums. >I wonder if you're timing out. What I know about Windows any more is >very close to zero, but my suspicion is that you might be building an >index or something that is taking a long time. You will have issued >a command, and then you wait for it to complete. If the time to >complete is longer than the time your settings are willing to wait, >then you can get in trouble. (This could also be due to an >intermediate firewall deciding that your session is "idle".)
- Previous message: [Slony1-general] Log Shipping with slony.
- Next message: [Slony1-general] Trouble with large DB and windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list