30 seconds may be too high but 1 second is too low from my experience. We had all sorts of missing content when we had our timeout set to 1.
I'd vote for something around 5 seconds. Bob Wicksall Systems Administrator Pioneer Library System 2557 State Rt. 21 Canandaigua, New York 14424 ----- Original Message ----- From: "Bill Erickson" <[email protected]> To: "Evergreen Development Discussion List" <[email protected]> Sent: Tuesday, June 14, 2011 8:41:59 AM GMT -05:00 US/Canada Eastern Subject: [OPEN-ILS-DEV] AC timeout change => [GIT] Evergreen ILS branch master updated. e08a5cbfaa14fcd386f63a5f3e29539e6be3f544 Hi Dan, I'd like to suggest we not make this change or at least make the default significantly lower. With a 30-second timeout and a slow or crippled added content provider, it would not take long for the Apache processes to be gobbled up, leaving EG unusable. My preference would be to keep it at 1 w/ the understanding that users can raise the value if they want to take that risk. If that's too aggressive for a default, I could maybe see using 2 or 3 seconds. Anything higher is unsafe, IMO. Of course, it depends on the environment. -b -------- Original Message -------- Subject: [open-ils-commits] [GIT] Evergreen ILS branch master updated. e08a5cbfaa14fcd386f63a5f3e29539e6be3f544 Date: Mon, 13 Jun 2011 15:37:26 -0400 (EDT) From: [email protected] (Evergreen Git) Reply-To: Evergreen Commits <[email protected]> To: [email protected] This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Evergreen ILS". The branch, master has been updated via e08a5cbfaa14fcd386f63a5f3e29539e6be3f544 (commit) from a66e257f791c550a00f3b927c2d34abf34a920e7 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit e08a5cbfaa14fcd386f63a5f3e29539e6be3f544 Author: Dan Scott <[email protected]> Date: Mon Jun 13 15:34:03 2011 -0400 Set a more generous AC timeout value A timeout value of 1 second is a bit too tight for many added content providers; set the default to 30 seconds to avoid too many artificial timeouts. Signed-off-by: Dan Scott <[email protected]> diff --git a/Open-ILS/examples/opensrf.xml.example b/Open-ILS/examples/opensrf.xml.example index a5d5a79..e41f477 100644 --- a/Open-ILS/examples/opensrf.xml.example +++ b/Open-ILS/examples/opensrf.xml.example @@ -288,7 +288,7 @@ vim:et:ts=4:sw=4: return data. Data not returned within the timeout is considered a failure --> - <timeout>1</timeout> + <timeout>30</timeout> <!-- After added content lookups have been disabled due to too many ----------------------------------------------------------------------- Summary of changes: Open-ILS/examples/opensrf.xml.example | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- Evergreen ILS _______________________________________________ open-ils-commits mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-commits
