Mon Sep 12 07:52:16 PDT 2016
- Previous message: [Slony1-general] Need some help again, keep alives, wide area replication , set failure
- Next message: [Slony1-general] sync performance
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello slony1 community, We’ve recently been testing communication reliability between our cluster nodes. Our config is a simple setup with one provider producing a modest volume of changes (measured in KB/s) consumed by 5 direct subscribers, though these are geographically distributed. The test is just a sync event followed by a wait on the sync originator. Example: cluster name = ams_cluster; node 5 admin conninfo='dbname=ams host=23.79.242.182 user=ams_slony sslmode=verify-ca sslcert=/usr/local/akamai/.ams_certs/complete-ams_slony.crt sslkey=/usr/local/akamai/.ams_certs/ams_slony.private_key sslrootcert=/usr/local/akamai/etc/ssl_ca/canonical_ca_roots.pem'; node 2 admin conninfo = 'dbname=ams user=ams_slony'; sync(id=2); wait for event (origin=2, confirmed=5, wait on=2, timeout=30); Tests show the script takes 10-20 secs to run on different nodes. Can anyone explain what’s happening internally during this time, and why it takes so long? On a healthy, lightly loaded system, we might have hoped for a sync response in just a couple seconds. Our slon daemons are running with mostly default startup options. Thanks in advance, Tom ☺ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20160912/f5b26e8e/attachment-0001.htm
- Previous message: [Slony1-general] Need some help again, keep alives, wide area replication , set failure
- Next message: [Slony1-general] sync performance
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list