# `qrtz_fired_triggers`

> 存储与已触发的Trigger相关的状态信息,以及相联 Job 的执行信息


- **Engine:** InnoDB
- **Collation:** utf8mb3_general_ci

## Columns

| # | Name | Type | Null | Key | Default | Extra | Comment |
|---|---|---|---|---|---|---|---|
| 1 | `SCHED_NAME` | `varchar(120)` | NO | PRI |  |  | 调度名称 |
| 2 | `ENTRY_ID` | `varchar(95)` | NO | PRI |  |  | 调度器实例id |
| 3 | `TRIGGER_NAME` | `varchar(200)` | NO |  |  |  | qrtz_triggers表trigger_name的外键 |
| 4 | `TRIGGER_GROUP` | `varchar(200)` | NO |  |  |  | qrtz_triggers表trigger_group的外键 |
| 5 | `INSTANCE_NAME` | `varchar(200)` | NO |  |  |  | 调度器实例名 |
| 6 | `FIRED_TIME` | `bigint` | NO |  |  |  | 触发的时间 |
| 7 | `SCHED_TIME` | `bigint` | NO |  |  |  | 定时器制定的时间 |
| 8 | `PRIORITY` | `int` | NO |  |  |  | 优先级 |
| 9 | `STATE` | `varchar(16)` | NO |  |  |  | 状态 |
| 10 | `JOB_NAME` | `varchar(200)` | YES |  |  |  | 集群中job的名字 |
| 11 | `JOB_GROUP` | `varchar(200)` | YES |  |  |  | 集群中job的所属组的名字 |
| 12 | `IS_NONCONCURRENT` | `varchar(1)` | YES |  |  |  | 是否并发 |
| 13 | `REQUESTS_RECOVERY` | `varchar(1)` | YES |  |  |  | 是否接受恢复执行，默认为false，设置了RequestsRecovery为true，则会被重新执行 |

## Indexes

| Name | Unique | Type | Columns |
|---|---|---|---|
| `IDX_QRTZ_FT_INST_JOB_REQ_RCVRY` |  | BTREE | `SCHED_NAME`, `INSTANCE_NAME`, `REQUESTS_RECOVERY` |
| `IDX_QRTZ_FT_J_G` |  | BTREE | `SCHED_NAME`, `JOB_NAME`, `JOB_GROUP` |
| `IDX_QRTZ_FT_JG` |  | BTREE | `SCHED_NAME`, `JOB_GROUP` |
| `IDX_QRTZ_FT_T_G` |  | BTREE | `SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP` |
| `IDX_QRTZ_FT_TG` |  | BTREE | `SCHED_NAME`, `TRIGGER_GROUP` |
| `IDX_QRTZ_FT_TRIG_INST_NAME` |  | BTREE | `SCHED_NAME`, `INSTANCE_NAME` |
| `PRIMARY` | ✓ | BTREE | `SCHED_NAME`, `ENTRY_ID` |

## Narrative

_No human-written narrative yet — when this table is exercised by a [vertical slice](../../slices/index.md), link from there back to this page._