西部数码主机 | 阿里云主机| 虚拟主机 | 服务器 | 返回乐道官网
当前位置: 主页 > 开发教程 > mysql教程 >

MySQL的表级别线程锁机制

时间:2016-11-14 16:12来源:未知 作者:好模板 点击:
本文基于MySQL 8.0的源代码总结了MySQL中表级别线程锁的实现机制, 底层仅关注Linux平台, Windows平台的实现可能有差异. 虽然不涉及到某个特定的存储引擎, 但会讨论MySQL的handler(实现plugin的

本文基于MySQL 8.0的源代码总结了MySQL中表级别线程锁的实现机制, 底层仅关注Linux平台, Windows平台的实现可能有差异. 虽然不涉及到某个特定的存储引擎, 但会讨论MySQL的handler(实现plugin的接口) API中与锁相关的部分.

数据结构

MySQL的锁实现是基于POSIX的read-lock 锁, 底层使用 mutex 和 conditional variable 等API实现. 为了避免死锁, 每个线程在访问数据前需要调用 thr_multi_lock()一次性获取所有相关表的锁, 一个线程可以持有多个表的锁.

为了便于理解, 需要区分一下 master lock 和 lock instance 两个概念: * master lock 是指每个table share结构中的 THR_LOCK 对象,也就是我们创建的每个表都有且仅有一个对应的 THR_LOCK 对象. * lock instance 是指每个open table handler 中的 THR_LOCK_DATA 对象, 也就是说多个线程并发访问一个表的时候, 每个线程需要有一个 THR_LOCK_DATA

可以这样简单的类比, 如果master lock对应一个磁盘文件, 那么lock instance对应了一个打开该文件的句柄FD.

数据结构定义如下:

typedef struct st_thr_lock_info
{
    my_thread_id thread_id;
    mysql_cond_t *suspend;
} THR_LOCK_INFO;

typedef struct st_thr_lock_data {
    THR_LOCK_INFO *owner;
    struct st_thr_lock_data *next,**prev;
    struct st_thr_lock *lock;
    mysql_cond_t *cond;
    enum thr_lock_type type;
    void *status_param;			/* Param to status functions */
    void *debug_print_param;
    struct PSI_table *m_psi;
} THR_LOCK_DATA;

struct st_lock_list {
    THR_LOCK_DATA *data,**last;
};

typedef struct st_thr_lock {
    LIST list;
    mysql_mutex_t mutex;
    struct st_lock_list read_wait;
    struct st_lock_list read;
    struct st_lock_list write_wait;
    struct st_lock_list write;
    ulong write_lock_count; /* incremented for write locks and reset on read locks */ 
    uint read_no_write_count;
    void (*get_status)(void*, int);	/* When one gets a lock */
    void (*copy_status)(void*,void*);
    void (*update_status)(void*); 	/* Before release of write */
    void (*restore_status)(void*);      /* Before release of read */
    my_bool (*check_status)(void *);
} THR_LOCK;

THR_LOCK

THR_LOCK 是每个表的多个实例共享的结构, 是锁管理的核心结构. 它的成员有:

  • list 链接到全局链表 thr_lock_thread_list 中的list node, 使用 mysqladmin debug 命令可以打印出所有的lock信息.
  • mutex 用于保护THR_LOCK对象自身的互斥量
  • read_wait/read/write_wait/write 持有以及等待读写锁的链表, 参见 THR_LOCK_DATA 结构的 next / prev 成员
  • write_lock_count 参考 max_write_lock_count 系统变量, 用于记录连续满足的写请求数, 以允许读请求在多个写请求期间得到满足. 因为默认某些写操作的优先级高于读, 连续的写请求会导致读请求饿死.
  • read_no_write_count 记录 TL_READ_NO_INSERT 锁类型的数目
  • void (*get_status)(void*, int) 等callback函数,用于实现 WRITE_CONCURRENT_INSERT 锁

THR_LOCK_DATA

THR_LOCK_DATA 的成员:

  • owner 指向所属的线程信息, 条件变量用于wake up该线程
  • next / prev 用于链表构造
  • lock 指向所属的 THR_LOCK 对象
  • cond 等待锁时指向 owner->suspend , 以唤起该线程
  • type 锁类型, 后面详细解释
  • status_param status functions 的参数
  • debug_print_param 用于打印调试信息
  • m_psi 用于performance schema instrumentation

锁类型和优先级

锁请求的类型定义如下:

enum thr_lock_type {
    TL_IGNORE=-1,
    TL_UNLOCK,			/* UNLOCK ANY LOCK */
    /*
       Parser only! At open_tables() becomes TL_READ or
       TL_READ_NO_INSERT depending on the binary log format
       (SBR/RBR) and on the table category (log table).
       Used for tables that are read by statements which
       modify tables.
       */
    TL_READ_DEFAULT,
    TL_READ,			/* Read lock */
    TL_READ_WITH_SHARED_LOCKS,
    /* High prior. than TL_WRITE. Allow concurrent insert */
    TL_READ_HIGH_PRIORITY,
    /* READ, Don't allow concurrent insert */
    TL_READ_NO_INSERT,
    /* 
       Write lock, but allow other threads to read / write.
       Used by BDB tables in MySQL to mark that someone is
       reading/writing to the table.
       */
    TL_WRITE_ALLOW_WRITE,
    /*
       parser only! Late bound low_priority_flag.
       At open_tables() becomes thd->insert_lock_default.
       */
    TL_WRITE_CONCURRENT_DEFAULT,
    /*
       WRITE lock used by concurrent insert. Will allow
       READ, if one could use concurrent insert on table.
       */
    TL_WRITE_CONCURRENT_INSERT,
    /* 
       parser only! Late bound low_priority flag. 
       At open_tables() becomes thd->update_lock_default.
       */
    TL_WRITE_DEFAULT,
    /* WRITE lock that has lower priority than TL_READ */
    TL_WRITE_LOW_PRIORITY,
    /* Normal WRITE lock */
    TL_WRITE,
    /* Abort new lock request with an error */
    TL_WRITE_ONLY
};

抛开parser-only类型, 这些类型的优先级从高到底排列如下:

  • TL_WRITE_ALLOW_WRITE
  • TL_WRITE_CONCURRENT_INSERT
  • TL_WRITE_LOW_PRIORITY
  • TL_READ
  • TL_WRITE
  • TL_READ_HIGH_PRIORITY
  • TL_WRITE_ONLY

同一类型的锁请求会按照FIFO(first-in-first-out)策略调度.

(责任编辑:好模板)
顶一下
(0)
0%
踩一下
(0)
0%
------分隔线----------------------------