[MDEV-34999] ha_innobase::open() should not acquire dict_sys.latch twice - Jira

XML

Word

Printable

Details

Type: Bug
Status: Open (View Workflow)
Priority: Major
Resolution: Unresolved
Affects Version/s: 10.11.8
Fix Version/s: 10.6, 10.11, 11.4
Component/s: Storage Engine - InnoDB
Labels:
- performance
Environment:
Debian Bookworm

Description

The following stack trace had to wait on dict_sys.latch:

ssux_lock_impl<false>::rd_wait()

dict_table_open_on_name(char const*, bool, dict_err_ignore_t)

dict_stats_update(dict_table_t*, dict_stats_upd_option_t)

ha_innobase::info_low(unsigned int, bool)

ha_innobase::open(char const*, int, unsigned int)

handler::ha_open(TABLE*, char const*, int, unsigned int, st_mem_root*, List<String>*)

(According to Marko Mäkelä: ) This one is an InnoDB bug. We certainly should not acquire and release a shared dict_sys.latch within a single ha_innobase::open().

Attachments

Issue Links

blocks

MDEV-34986 Use RAII classes to manage locks

In Review

relates to

MDEV-35000 dict_table_close() is a performance hog

In Progress

MDEV-35154 dict_sys_t::load_table() is holding exclusive dict_sys.latch for unnecessarily long time

Confirmed

MDEV-35436 dict_stats_fetch_from_ps() unnecessarily acquires exclusive dict_sys.latch

Open

MDEV-34988 InnoDB locks dict_sys.latch for a long time during ALTER TABLE

Open

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Max Kellermann

Votes:: 1 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2024-09-24 09:00

Updated:: 2024-12-10 16:25

Git Integration

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