Details
-
Technical task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Done
-
None
-
None
Description
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. Setting the variable to 1 (semi-table lock) would result in poor performance and it is rare to use non-transactional engines these days. Further, maintaining the variable complicates the code.
The variable, spider_semi_table_lock_connection, should be too deprecated because it is for tweaking the semi-table locking.
See https://mariadb.com/kb/en/spider-server-system-variables/ for the details of the variables.
Attachments
Issue Links
- blocks
-
MDEV-28830
Delete spider_semi_table_lock and spider_semi_table_lock_connection and related code
-
- Open
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 10.7 [ 24805 ] |
| Description | TBD: should default value changed? |
| Description | TBD: should default value changed? | TBD: should the default value be changed? |
| Description | TBD: should the default value be changed? | The default value should be changed to 0. |
| Description | The default value should be changed to 0. |
The default value should be changed to 0. |
| Description |
The default value should be changed to 0. |
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. That is because it is rare to use non-transactional engines these days and the option complicates connection handling. |
| Description | We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. That is because it is rare to use non-transactional engines these days and the option complicates connection handling. |
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. That is because it is rare to use non-transactional engines these days and the option complicates connection handling.
See https://mariadb.com/kb/en/spider-server-system-variables/#spider_semi_table_lock for the details of the variable. |
| Description |
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. That is because it is rare to use non-transactional engines these days and the option complicates connection handling.
See https://mariadb.com/kb/en/spider-server-system-variables/#spider_semi_table_lock for the details of the variable. |
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. Setting the variable to 1 (semi-table lock) would result in poor performance and it is rare to use non-transactional engines these days. Further, maintaining the variable complicates the code.
See https://mariadb.com/kb/en/spider-server-system-variables/#spider_semi_table_lock for the details of the variable. |
| Summary | Deprecate spider_semi_table_lock | Deprecate spider_semi_table_lock and spider_semi_table_lock_connection |
| Description |
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. Setting the variable to 1 (semi-table lock) would result in poor performance and it is rare to use non-transactional engines these days. Further, maintaining the variable complicates the code.
See https://mariadb.com/kb/en/spider-server-system-variables/#spider_semi_table_lock for the details of the variable. |
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. Setting the variable to 1 (semi-table lock) would result in poor performance and it is rare to use non-transactional engines these days. Further, maintaining the variable complicates the code.
The variable, spider_semi_table_lock_connection, should be too deprecated because it is for tweaking semi-table locking. See https://mariadb.com/kb/en/spider-server-system-variables/#spider_semi_table_lock for the details of the variable. |
| Description |
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. Setting the variable to 1 (semi-table lock) would result in poor performance and it is rare to use non-transactional engines these days. Further, maintaining the variable complicates the code.
The variable, spider_semi_table_lock_connection, should be too deprecated because it is for tweaking semi-table locking. See https://mariadb.com/kb/en/spider-server-system-variables/#spider_semi_table_lock for the details of the variable. |
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. Setting the variable to 1 (semi-table lock) would result in poor performance and it is rare to use non-transactional engines these days. Further, maintaining the variable complicates the code.
The variable, spider_semi_table_lock_connection, should be too deprecated because it is for tweaking the semi-table locking. See https://mariadb.com/kb/en/spider-server-system-variables/#spider_semi_table_lock for the details of the variable. |
| Description |
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. Setting the variable to 1 (semi-table lock) would result in poor performance and it is rare to use non-transactional engines these days. Further, maintaining the variable complicates the code.
The variable, spider_semi_table_lock_connection, should be too deprecated because it is for tweaking the semi-table locking. See https://mariadb.com/kb/en/spider-server-system-variables/#spider_semi_table_lock for the details of the variable. |
We change the default value of the plugin variable, spider_semi_table_lock, to 0 (no semi-table lock) and then deprecate the variable. Setting the variable to 1 (semi-table lock) would result in poor performance and it is rare to use non-transactional engines these days. Further, maintaining the variable complicates the code.
The variable, spider_semi_table_lock_connection, should be too deprecated because it is for tweaking the semi-table locking. See https://mariadb.com/kb/en/spider-server-system-variables/ for the details of the variables. |
| Link | This issue blocks MDEV-28830 [ MDEV-28830 ] |
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Priority | Critical [ 2 ] | Major [ 3 ] |
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Priority | Critical [ 2 ] | Major [ 3 ] |
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
holyfoot Please review: https://github.com/MariaDB/server/commit/b501e60a7f140667e7c066d76d0bf8dcf2132951
| Assignee | Nayuta Yanagisawa [ JIRAUSER47117 ] | Alexey Botchkov [ holyfoot ] |
| Status | In Progress [ 3 ] | In Review [ 10002 ] |
| Assignee | Alexey Botchkov [ holyfoot ] | Nayuta Yanagisawa [ JIRAUSER47117 ] |
| Status | In Review [ 10002 ] | Stalled [ 10000 ] |
| Fix Version/s | 10.7.5 [ 27505 ] | |
| Fix Version/s | 10.8.4 [ 27503 ] | |
| Fix Version/s | 10.9.2 [ 27115 ] | |
| Fix Version/s | 10.7 [ 24805 ] | |
| Fix Version/s | 10.8 [ 26121 ] | |
| Fix Version/s | 10.9 [ 26905 ] | |
| Resolution | Done [ 10200 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
The issue is critical because MDEV-28830 is critical.