Markus Mäkelä 21eef8a670
MXS-1985: Kill connections inside workers
The LocalClient micro-client required a reference to the session that was
valid at construction time. This is the reason why the previous
implementation used dcb_foreach to first gather the targets and then
execute queries on them. By replacing this reference with pointers to the
raw data it requires, we lift the requirement of the orignating session
being alive at construction time.

Now that the LocalClient no longer holds a reference to the session, the
killing of the connection does not have to be done on the same thread that
started the process. This prevents the deadlock that occurred when
concurrect dcb_foreach calls were made.

Replaced the unused dcb_foreach_parallel with a version of dcb_foreach
that allows iteration of DCBs local to this worker. The dcb_foreach_local
is the basis upon which all DCB access outside of administrative tasks
should be built on.

This change will introduce a regression in functionality: The client will
no longer receive an error if no connections match the KILL query
criteria. This is done to avoid having to synchronize the workers after
they have performed the killing of their own connections.
2018-07-24 09:51:46 +03:00
2018-03-07 10:43:07 +02:00
2017-07-03 17:08:39 +03:00
2018-07-05 12:01:38 +03:00
2018-04-24 12:39:22 +03:00
2018-04-27 18:15:19 +03:00
2018-04-17 09:34:12 +03:00
2018-07-18 16:28:45 +03:00
2018-07-17 13:05:52 +03:00
2017-11-27 09:10:33 +02:00
2017-06-01 10:24:20 +03:00
2018-06-11 09:17:02 +03:00
2018-01-16 09:47:49 +02:00
2017-05-29 21:50:29 +03:00
2017-06-01 19:39:41 +03:00
2017-06-01 10:42:21 +03:00
2018-07-07 09:27:34 +03:00
2017-06-20 10:45:02 +03:00
2018-04-24 10:18:19 +03:00
2018-07-05 09:44:13 +03:00

MaxScale by MariaDB Corporation

Build Status

The MariaDB Corporation MaxScale is an intelligent proxy that allows forwarding of database statements to one or more database servers using complex rules, a semantic understanding of the database statements and the roles of the various servers within the backend cluster of databases.

MaxScale is designed to provide load balancing and high availability functionality transparently to the applications. In addition it provides a highly scalable and flexible architecture, with plugin components to support different protocols and routing decisions.

For a detailed overview of what MaxScale can do, read the MaxScale page on the MariaDB website.

An Google Group exists for MaxScale that can be used to discuss ideas, issues and communicate with the MaxScale community.

We're also on the #maria and #maxscale channels on FreeNode.

Please report all feature requests, improvements and bugs in the MariaDB Jira.

Getting Started

Read the Documentation Overview for a list of all MaxScale documents.

Documentation

The official documentation can be found on the MariaDB Knowledge Base.

A MaxScale Troubleshooting Guide can be found on the MariaDB Knowledgebase. It answers common questions encountered when installing and using MaxScale.

The documentation can also be found in the Documentation directory of the source tree.

Contributing Code

Read the Contributing page on the wiki for more information on how to do pull request and where to do them.

Description
No description provided
Readme 118 MiB
Languages
C 50.9%
C++ 30.8%
Shell 3.7%
HTML 3.2%
Tcl 3.1%
Other 8.1%