[GitHub] [storm] ysyyork commented on a change in pull request #2981: Issue tracker [STORM-3362] Solved: eventHubSpout uses a blocking receiver in nextTuple()

[GitBox <gi...@apache.org>]

ysyyork 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_r270051556
 
 

 ##########
 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:
   you are right. I think this depends on the how big is your payload in event hub. eventhub has a 1 MB limit for packet size. If we considering worst case scenario, then the bandwidth requirements are 1MB/0.01sec = 100M/sec which seems a really high requirements. based on this, let's tune this to like 100mills so the bandwidth requirements become 10M/sec. do you think this is reasonable? let me know. My current application, the payload is pretty small. only like several bytes so it doesn't matter. 

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services