alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DOC-fix-xrefs Fix broken links

Browse Source
This commit is contained in:
Fintan Bolton 2019-11-27 16:01:06 +01:00 committed by Chris Cranford
parent ebfbd83a90
commit f45215ef69
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/modules/ROOT/pages/modules/cdc-mysql-connector/c_how-the-mysql-connector-performs-database-snapshots.adoc
View File

@ -56,7 +56,7 @@ a| Records the completed snapshot in the connector offsets.
If the connector fails, stops, or is rebalanced while making the _initial snapshot_, the connector creates a new snapshot once restarted. Once that _intial snapshot_ is completed, the {prodname} MySQL connector restarts from the same position in the binlog so it does not miss any updates.
NOTE: If the connector stops for long enough, MySQL could purge old binlog files and the connector's position would be lost. If the position is lost, the connecotr reverts to the _initial snapshot_ for its starting position. For more tips on troubleshooting the {prodname} MySQL connector, see xref:assemblies/cdc-mysql-connector/as_connector-common-issues.adoc[the MySQL connector common issues].
NOTE: If the connector stops for long enough, MySQL could purge old binlog files and the connector's position would be lost. If the position is lost, the connecotr reverts to the _initial snapshot_ for its starting position. For more tips on troubleshooting the {prodname} MySQL connector, see <<connector-common-issues>>.
== What if Global Read Locks are not allowed?
[[no-global-read-lock-mysql-connect_{context}]]

2
documentation/modules/ROOT/pages/modules/cdc-mysql-connector/p_create-a-mysql-user-for-cdc.adoc
View File

@ -29,7 +29,7 @@ mysql> GRANT SELECT, RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIE
TIP: See xref:permissions-explained-mysql-connector[permissions explained] for notes on each permission.
IMPORTANT: If using a hosted option such as Amazon RDS or Amazon Aurora that do not allow a *global read lock*, table-level locks are used to create the _consistent snapshot_. In this case, you need to also grant `LOCK_TABLES` permissions to the user that you create. See xref:assemblies/cdc-mysql-connector/as_overview-of-how-mysql-works.adoc[What to do with no global read lock] for more details.
IMPORTANT: If using a hosted option such as Amazon RDS or Amazon Aurora that do not allow a *global read lock*, table-level locks are used to create the _consistent snapshot_. In this case, you need to also grant `LOCK_TABLES` permissions to the user that you create. See <<overview-of-how-the-mysql-connector-works>> for more details.
[start=3]
. Finalize the user's permissions:

2
documentation/modules/ROOT/pages/modules/cdc-mysql-connector/p_install-the-mysql-connector.adoc
View File

@ -1,7 +1,7 @@
// Metadata created by nebel
//
[id="install-the-mysql-connector-{context}"]
[id="install-the-mysql-connector_{context}"]
= Installing the MySQL connector
Installing the {prodname} MySQL connector is a simple process whereby you only need to download the JAR, extract it to your Kafka Connect environment, and ensure the plugin's parent directory is specified in your Kafka Connect environment.