azure - EventHub Trigger to Functions cardinality with one causing higher timeouts -


when select many "cardinality" in function bindings, works fine.

{   "bindings": [     {       "type": "eventhubtrigger",       "name": "eventhubmessages",       "direction": "in",       "path": "sessions",       "connection": "connectionstring",       "cardinality": "many",       "consumergroup": "group1"     }   ],   "disabled": false } 

when select "one" in function bindings, getting higher timeouts.

   "cardinality": "one", 

when @ console, see there multiple functions started,

2017-09-12t19:37:49.645 function started (id=f0ef1cd5-8331-448e-86c6-84c745bbab13) 2017-09-12t19:37:49.956 function started (id=26629395-54b8-4f83-9852-b3d55307318b) 

is cardinality "many" single threaded, , "one" getting processed parallely. while have no problem parallel processing, brings higher timeouts. or core issue functions app?

the total "function started", see close 250. scalability manager having issue here?

cardinality 'one' means 1 function invocation per eventdata payload. 'many' means whole batch of eventdata[] per invocation. there's more detail on wiki @ https://github.com/azure/azure-webjobs-sdk/wiki/eventhub-support

when reasoning correctness of code, should function invocations could run in parallel , batch sizes random (unless you're explicitly configuring that). single batch still run serially.


Comments

Popular posts from this blog

ios - MKAnnotationView layer is not of expected type: MKLayer -

ZeroMQ on Windows, with Qt Creator -

unity3d - Unity SceneManager.LoadScene quits application -