azure stream analytics query too complex??? not giving proper output and now error... what to do next....

Rocksde 106 Reputation points
2020-08-23T16:45:24.557+00:00

Hi,
Query I use attached.

I am using an event hub to ingest messages in json format from a push api. Json msg has some arrays in it. Now I am getting an error like "We cannot connect to Event Hub partition [0] because the maximum number of allowed receivers per partition in a consumer group has been reached. Ensure that other Stream Analytics jobs or Service Bus Explorer are not using the same consumer group. The following information may be helpful in identifying the connected receivers: Exceeded the maximum number of allowed receivers per partition in a consumer group which is 5".

I want the output to go to Azure Table Storage which works as long as the query works properly.

I got it to work before when it was not that complex but now it seems I cannot join all the needed results back to the main serviceProblem output. and sometimes the query runs successfully but some of the output are blank although the should not be. should i split the query over more ASA jobs or should I push some of the outputs through another event hub to avoid the error? thanks for your help.

19676-myquery.txt

Azure Table Storage
Azure Table Storage
An Azure service that stores structured NoSQL data in the cloud.
156 questions
Azure Event Hubs
Azure Event Hubs
An Azure real-time data ingestion service.
559 questions
Azure Stream Analytics
Azure Stream Analytics
An Azure real-time analytics service designed for mission-critical workloads.
331 questions
0 comments No comments
{count} votes

Accepted answer
  1. Rocksde 106 Reputation points
    2020-08-24T19:58:16.287+00:00

    So others know what I did, I found the following troubleshooting doc suggesting for maximum number of allowed receivers per partition to reconstruct the query such as try using union or different inputs from different consumer groups in the same job. for the moment I actually use several consumer groups as well as different jobs which solved my problem an i could reduce the SU per job so impacting the SU overall drastically.

    2 people found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful