Dapr invoke binding with Event Hub publishes multiple messages

[arkakk93]

Description For each event that I publish using Azure Event Hub binding, there are several events that get published to the event hub. The service is deployed on AKS cluster

Using following to publish: await this.daprClient.InvokeBindingAsync("componentName", "create", object, new Dictionary<string, string> { { "partitionKey", "someId"} });

Details Component Used

apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: componentName namespace: spec: type: bindings.azure.eventhubs version: v1 metadata: - name: connectionString # Azure EventHubs connection string secretKeyRef: name: keyName key: keyName - name: consumerGroup value: consumerGroup - name: storageAccountName # Azure Storage Account Name value: "storageAccountName" - name: storageAccountKey # Azure Storage Account Key secretKeyRef: name: storageAccountKey key: storageAccountKey - name: storageContainerName # Azure Storage Container Name value: "storageContainerName" auth: secretStore: keyvaultsecretstore

Also this component is used by another service to subscribe to this event hub. Reason for using binding and not Pub/Sub component here: Based on issue that mentions pub/sub component is being re-written.

SDK version being used: Dapr.AspNetCore - Version="1.3.0" Dapr version on AKS cluster: 1.4.3

[arkakk93]

This is happening when the load is increased With one or two messages, it seems to be working fine

Is this the correct setup? Like mentioned above same binding is used by one service to publish and other to subscribe. Should each service have different components for binding (and Invoke binding) to work correctly?

[mukundansundar]

@berndverst @halspang I think this issue should be moved to components-contrib ... ?

[halspang]

@mukundansundar - I think you're right. This may need to be moved over to components-contrib. I was hoping to get a chance to investigate it but haven't had time to setup my own environment pointing at EventHub.

[i-am-shodan]

I can confirm that we are seeing this issue in our production environment

[i-am-shodan]

As a test i've tried using the eventhub pubsub component. That hasn't demonstrated any issues.

[arkakk93]

As a test i've tried using the eventhub pubsub component. That hasn't demonstrated any issues.

What version of Dapr and Dapr SDK(.NET) did you use for this?

[mukundansundar]

@berndverst @halspang Can you move this issue to components-contrib ... I do not have permissions for that.

I think then this issue can be triaged to be picked up ...

[i-am-shodan]

Dapr 1.6.0. SDK and runtime both match,

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[robeving]

I'm still seeing this issue

[berndverst]

I'm still seeing this issue

@robeving are you seeing this with 1.8.0-rc.3 by chance? (That was released just a few days ago)

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[robeving]

Can confirm that this issue still seems present in 1.8 - have received double data in our eventhub

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[i-am-shodan]

still broken

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[dapr-bot]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.