You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ignite.apache.org by "shishkovilja (via GitHub)" <gi...@apache.org> on 2023/04/10 10:36:15 UTC
[GitHub] [ignite] shishkovilja commented on a diff in pull request #10488: IGNITE-18574 CDC: add documentation about Kafka request timeouts
shishkovilja commented on code in PR #10488:
URL: https://github.com/apache/ignite/pull/10488#discussion_r1161620359
##########
docs/_docs/extensions-and-integrations/change-data-capture-extensions.adoc:
##########
@@ -113,6 +113,14 @@ image:../../assets/images/integrations/CDC-ignite2kafka.svg[]
| `kafkaRequestTimeout` | Kafka request timeout in milliseconds. | `3000`
|===
+`kafkaRequestTimeout` property sets how much `IgniteToKafkaCdcStreamer` will wait for `KafkaProducer` to finish request.
+
+NOTE: _Too low value_ of this timeout can lead to frequent failures of `IgniteToKafkaCdcStreamer`
Review Comment:
Good point!
##########
docs/_docs/extensions-and-integrations/change-data-capture-extensions.adoc:
##########
@@ -175,6 +183,16 @@ Kafka to Ignite configuration file should contain the following beans that will
| `threadCount` | Count of threads to proceed consumers. Each thread poll records from dedicated partitions in round-robin manner. | 16
|===
+`kafkaRequestTimeout` property sets timeouts for a following `KafkaConsumer` operations:
+
+- Poll from event and metadata topics.
+- Offsets commit.
+- Closing of a consumer.
+- Offsets request (during metadata updates).
+- Metadata topic partitions request (during metadata updater start).
+
+NOTE: _Too low value_ of `kafkaRequestTimeout` can lead to frequent failures of `kafka-to-ignite.sh` because of possible delays in network or on Kafka broker. Also, proper `KafkaConsumer` configuration should be provided, including link:https://kafka.apache.org/documentation/#consumerconfigs_request.timeout.ms[request.timeout.ms]. For more details you should refer to a link:https://kafka.apache.org/documentation/#configuration[configuration] section of the official Kafka documentation.
Review Comment:
Good point!
##########
docs/_docs/extensions-and-integrations/change-data-capture-extensions.adoc:
##########
@@ -175,6 +183,16 @@ Kafka to Ignite configuration file should contain the following beans that will
| `threadCount` | Count of threads to proceed consumers. Each thread poll records from dedicated partitions in round-robin manner. | 16
|===
+`kafkaRequestTimeout` property sets timeouts for a following `KafkaConsumer` operations:
+
+- Poll from event and metadata topics.
Review Comment:
Timeouts for `#poll` are, of cause, is on the surface. But I think, that we can at least tell about request types, that they are affected by a timeout, because they can (unlike `#poll`) raise timeout exceptions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org