Skip to content

Commit 07f8d6b

Browse files
Merge pull request #4397 from SudheeshGH/spudpate
HA Event Scheduler Details
2 parents 63704f5 + 8c5d1ea commit 07f8d6b

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

articles/mysql/flexible-server/concepts-server-parameters.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -391,10 +391,6 @@ DO
391391
<your statement>;
392392
```
393393

394-
#### Limitations
395-
396-
For servers with high availability configured, when failover occurs, it's possible that the `event_scheduler` server parameter is set to `OFF`. If this occurs, when the failover is complete, configure the parameter to set the value to `ON`.
397-
398394
### innodb_ft_user_stopword_table
399395
`innodb_ft_user_stopword_table` is a server parameter in MySQL that specifies the name of the table containing custom stopwords for InnoDB Full-Text Search. The table must be in the same database as the full-text indexed table, and its first column must be of type `VARCHAR`. In Azure Database for MySQL - Flexible Server, the default setting of `sql_generate_invisible_primary_key=ON` causes all tables without an explicit primary key to automatically include an invisible primary key. This behavior conflicts with the requirements for `innodb_ft_user_stopword_table`, as the invisible primary key becomes the first column of the table, preventing it from functioning as intended during Full-Text Search. To resolve this issue, you must set `sql_generate_invisible_primary_key=OFF` in the same session before creating the custom stopword table. For example:
400396

0 commit comments

Comments
 (0)