THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below.
User who did this - Morten Tryfoss (mtryfoss) Attached to Project - sip-router Summary - Improvement for db_cluster Task Type - Improvement Category - Module Status - Unconfirmed Assigned To - Operating System - All Severity - Medium Priority - Normal Reported Version - 4.1 Due in Version - Undecided Due Date - Undecided Details - I've been testing db_cluster for a while. The goal is to always be sure that kamailio got a responsive db backend. We run db_cluster with parallell write and serial read for mainly auth and registrar functionality. This works well in normal situations, but the error handler is not very good. For example, a primary key insert that fails will disable the connection from the pool for "inactive_interval" of time. Of course the best would be to ignore specific error codes, but that is a pretty large job. This patch tries to address this problem by introducing a new parameter: max_query_length It will not change the timout of the query, but only disable the connection from the pool if a failed query has been running for more than "max_query_length" seconds. In my opinion we don't need to disable a connection if it is responsive. Please have a look and give feedback. One or more files have been attached. More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=405 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
