HeartSaVioR commented on a change in pull request #2981: Issue tracker
[STORM-3362] Solved: eventHubSpout uses a blocking receiver in nextTuple()
URL: https://github.com/apache/storm/pull/2981#discussion_r269917143
##########
File path:
external/storm-eventhubs/src/main/java/org/apache/storm/eventhubs/spout/EventHubSpoutConfig.java
##########
@@ -42,6 +42,7 @@
// disabling filter
private String connectionString;
private String topologyName;
+ private int receiverTimeoutInMillis = 10; // default
Review comment:
Is `10ms` a realistic value for timeout? Since it's the default value and
end users don't touch unless they face timeout error, the value would need to
cover most of cases. We know it should be short to let Spout handles ack/fail
fast, but `10ms` sounds too small to reach remote-end.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
