Fri Jan 4 15:05:52 PST 2008
- Previous message: [Slony1-commit] slony1-engine RELEASE
- Next message: [Slony1-commit] slony1-engine/src/slonik Makefile slonik.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide In directory main.slony.info:/tmp/cvs-serv13699 Modified Files: faq.sgml Log Message: Add notes to FAQ concerning findings for bug #27 Index: faq.sgml =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/faq.sgml,v retrieving revision 1.72 retrieving revision 1.73 diff -C2 -d -r1.72 -r1.73 *** faq.sgml 11 Dec 2007 21:27:31 -0000 1.72 --- faq.sgml 4 Jan 2008 23:05:50 -0000 1.73 *************** *** 1374,1377 **** --- 1374,1396 ---- </answer> </qandaentry> + <qandaentry> + + <question><para> I'm noticing in the logs that a &lslon; is frequently + switching in and out of <quote>polling</quote> mode as it is + frequently reporting <quote>LISTEN - switch from polling mode to use + LISTEN</quote> and <quote>UNLISTEN - switch into polling + mode</quote>. </para> </question> + + <answer><para> The thresholds for switching between these modes are + controlled by the configuration parameters <xref + linkend="slon-config-sync-interval"> and <xref + linkend="slon-config-sync-interval-timeout">; if the timeout value + (which defaults to 10000, implying 10s) is kept low, that makes it + easy for the &lslon; to decide to return to <quote>listening</quote> + mode. You may want to increase the value of the timeout + parameter. </para> + </answer> + </qandaentry> + </qandadiv> <qandadiv id="faqbugs"> <title> &slony1; FAQ: &slony1; Bugs in Elder Versions </title>
- Previous message: [Slony1-commit] slony1-engine RELEASE
- Next message: [Slony1-commit] slony1-engine/src/slonik Makefile slonik.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list