[MDEV-5597] Reduce usage of LOCK_open: LOCK_flush - Jira

XML

Word

Printable

Details

Type: Task
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Fix Version/s: 10.0.9
Component/s: None
Labels:
None

Description

There is relationship between LOCK_flush and LOCK_open. Even though it is not on a hot path, it indirectly interferes with TABLE_SHARE::tdc.flushed. The latter is on hot path and will eventually be moved out of LOCK_open.

The sole purpose of LOCK_flush is to let tdc_remove_table() wait for concurrent FLUSH TABLES. Replace global rwlock with per-share condition variable.

Attachments

Issue Links

relates to

MDEV-4702 Reduce usage of LOCK_open

Closed

MDEV-4956 Reduce usage of LOCK_open: TABLE_SHARE::tdc.used_tables

Closed

MDEV-5388 Reduce usage of LOCK_open: unused_tables

Closed

MDEV-5403 Reduce usage of LOCK_open: tc_count

Closed

MDEV-5492 Reduce usage of LOCK_open: TABLE::in_use

Closed

MDEV-5864 Reduce usage of LOCK_open: TABLE_SHARE::tdc.free_tables

Closed

(1 relates to)

Activity

People

Assignee:: Sergey Vojtovich

Reporter:: Sergey Vojtovich

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2014-01-31 11:04

Updated:: 2014-03-14 18:17

Resolved:: 2014-02-13 12:17

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.