DBZ-7902: Added Docs changes for streaming.delay.ms
This commit is contained in:
parent
6dbe5cbed1
commit
e33d788639
@ -2873,6 +2873,10 @@ Heartbeat messages are useful when there are many updates in a database that is
|
||||
|No default
|
||||
|An interval in milliseconds that the connector should wait before performing a snapshot when the connector starts. If you are starting multiple connectors in a cluster, this property is useful for avoiding snapshot interruptions, which might cause re-balancing of connectors.
|
||||
|
||||
|[[db2-property-streaming-delay-ms]]<<db2-property-streaming-delay-ms, `+streaming.delay.ms+`>>
|
||||
|0
|
||||
|An interval in milliseconds that the connector should wait before initiating the streaming process after completing the snapshot. This delay helps prevent the connector from re-snapshotting if it encounters a failure immediately after finishing the snapshot and before starting the streaming process. Set this value higher than the `offset.flush.interval.ms` property of the Connect worker to ensure sufficient delay.
|
||||
|
||||
|[[db2-property-snapshot-include-collection-list]]<<db2-property-snapshot-include-collection-list, `+snapshot.include.collection.list+`>>
|
||||
| All tables specified in `table.include.list`
|
||||
|An optional, comma-separated list of regular expressions that match the fully-qualified names (`_<schemaName>.<tableName>_`) of the tables to include in a snapshot.
|
||||
|
@ -2469,6 +2469,10 @@ Enable the connector to send heartbeat messages to ensure that it sends the late
|
||||
|An interval in milliseconds that the connector should wait before performing a snapshot when the connector starts.
|
||||
If you start multiple connectors in a cluster, this property is useful for avoiding snapshot interruptions, which might cause re-balancing of connectors.
|
||||
|
||||
|[[informix-property-streaming-delay-ms]]<<informix-property-streaming-delay-ms, `+streaming.delay.ms+`>>
|
||||
|0
|
||||
|An interval in milliseconds that the connector should wait before initiating the streaming process after completing the snapshot. This delay helps prevent the connector from re-snapshotting if it encounters a failure immediately after finishing the snapshot and before starting the streaming process. Set this value higher than the `offset.flush.interval.ms` property of the Connect worker to ensure sufficient delay.
|
||||
|
||||
|[[informix-property-snapshot-include-collection-list]]<<informix-property-snapshot-include-collection-list, `+snapshot.include.collection.list+`>>
|
||||
| All tables specified in `table.include.list`
|
||||
|An optional, comma-separated list of regular expressions that match the fully-qualified names (`_databaseName_._schemaName_._tableName_`) of the tables to include in a snapshot.
|
||||
|
@ -1920,6 +1920,10 @@ For each collection that you specify, also specify another configuration propert
|
||||
|An interval in milliseconds that the connector should wait before taking a snapshot after starting up; +
|
||||
Can be used to avoid snapshot interruptions when starting multiple connectors in a cluster, which may cause re-balancing of connectors.
|
||||
|
||||
|[[mongodb-property-streaming-delay-ms]]<<mongodb-property-streaming-delay-ms, `+streaming.delay.ms+`>>
|
||||
|0
|
||||
|An interval in milliseconds that the connector should wait before initiating the streaming process after completing the snapshot. This delay helps prevent the connector from re-snapshotting if it encounters a failure immediately after finishing the snapshot and before starting the streaming process. Set this value higher than the `offset.flush.interval.ms` property of the Connect worker to ensure sufficient delay.
|
||||
|
||||
|[[mongodb-property-snapshot-fetch-size]]<<mongodb-property-snapshot-fetch-size, `+snapshot.fetch.size+`>>
|
||||
|`0`
|
||||
|Specifies the maximum number of documents that should be read in one go from each collection while taking a snapshot.
|
||||
|
@ -3748,6 +3748,10 @@ The connector might establish JDBC connections at its own discretion, so this pr
|
||||
|No default
|
||||
|An interval in milliseconds that the connector should wait before performing a snapshot when the connector starts. If you are starting multiple connectors in a cluster, this property is useful for avoiding snapshot interruptions, which might cause re-balancing of connectors.
|
||||
|
||||
|[[mysql-property-streaming-delay-ms]]<<mysql-property-streaming-delay-ms, `+streaming.delay.ms+`>>
|
||||
|0
|
||||
|An interval in milliseconds that the connector should wait before initiating the streaming process after completing the snapshot. This delay helps prevent the connector from re-snapshotting if it encounters a failure immediately after finishing the snapshot and before starting the streaming process. Set this value higher than the `offset.flush.interval.ms` property of the Connect worker to ensure sufficient delay.
|
||||
|
||||
|[[mysql-property-snapshot-fetch-size]]<<mysql-property-snapshot-fetch-size, `+snapshot.fetch.size+`>>
|
||||
|No default
|
||||
|During a snapshot, the connector reads table content in batches of rows. This property specifies the maximum number of rows in a batch.
|
||||
|
@ -3793,6 +3793,10 @@ After the connector inserts records into the configured table, it is able to rec
|
||||
|Specifies an interval in milliseconds that the connector waits after it starts before it takes a snapshot. +
|
||||
Use this property to prevent snapshot interruptions when you start multiple connectors in a cluster, which might cause re-balancing of connectors.
|
||||
|
||||
|[[oracle-property-streaming-delay-ms]]<<oracle-property-streaming-delay-ms, `+streaming.delay.ms+`>>
|
||||
|0
|
||||
|An interval in milliseconds that the connector should wait before initiating the streaming process after completing the snapshot. This delay helps prevent the connector from re-snapshotting if it encounters a failure immediately after finishing the snapshot and before starting the streaming process. Set this value higher than the `offset.flush.interval.ms` property of the Connect worker to ensure sufficient delay.
|
||||
|
||||
|[[oracle-property-snapshot-fetch-size]]<<oracle-property-snapshot-fetch-size, `+snapshot.fetch.size+`>>
|
||||
|`10000`
|
||||
|Specifies the maximum number of rows that should be read in one go from each table while taking a snapshot.
|
||||
|
@ -3551,6 +3551,10 @@ become outdated if TOASTable columns are dropped from the table.
|
||||
|No default
|
||||
|An interval in milliseconds that the connector should wait before performing a snapshot when the connector starts. If you are starting multiple connectors in a cluster, this property is useful for avoiding snapshot interruptions, which might cause re-balancing of connectors.
|
||||
|
||||
|[[postgresql-property-streaming-delay-ms]]<<postgresql-property-streaming-delay-ms, `+streaming.delay.ms+`>>
|
||||
|0
|
||||
|An interval in milliseconds that the connector should wait before initiating the streaming process after completing the snapshot. This delay helps prevent the connector from re-snapshotting if it encounters a failure immediately after finishing the snapshot and before starting the streaming process. Set this value higher than the `offset.flush.interval.ms` property of the Connect worker to ensure sufficient delay.
|
||||
|
||||
|[[postgresql-property-snapshot-fetch-size]]<<postgresql-property-snapshot-fetch-size, `+snapshot.fetch.size+`>>
|
||||
|`10240`
|
||||
|During a snapshot, the connector reads table content in batches of rows. This property specifies the maximum number of rows in a batch.
|
||||
|
@ -3066,6 +3066,10 @@ Disabled by default.
|
||||
|An interval in milli-seconds that the connector should wait before taking a snapshot after starting up; +
|
||||
Can be used to avoid snapshot interruptions when starting multiple connectors in a cluster, which may cause re-balancing of connectors.
|
||||
|
||||
|[[sqlserver-property-streaming-delay-ms]]<<sqlserver-property-streaming-delay-ms, `+streaming.delay.ms+`>>
|
||||
|0
|
||||
|An interval in milliseconds that the connector should wait before initiating the streaming process after completing the snapshot. This delay helps prevent the connector from re-snapshotting if it encounters a failure immediately after finishing the snapshot and before starting the streaming process. Set this value higher than the `offset.flush.interval.ms` property of the Connect worker to ensure sufficient delay.
|
||||
|
||||
|[[sqlserver-property-snapshot-fetch-size]]<<sqlserver-property-snapshot-fetch-size, `+snapshot.fetch.size+`>>
|
||||
|`2000`
|
||||
|Specifies the maximum number of rows that should be read in one go from each table while taking a snapshot.
|
||||
|
Loading…
Reference in New Issue
Block a user