Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Geo-DR Alias in ServiceBus-Triggers #2037

Open
tohling opened this issue Nov 28, 2018 · 5 comments
Open

Add support for Geo-DR Alias in ServiceBus-Triggers #2037

tohling opened this issue Nov 28, 2018 · 5 comments

Comments

@tohling
Copy link

tohling commented Nov 28, 2018

When customer configures a ServiceBus-Trigger with a Geo-DR Alias enabled Service Bus connection string and a failover occurs on Service Bus side, the Function fails to execute and will continuously throw the following error,

Microsoft.ServiceBus.Messaging.MessagingEntityNotFoundException : 40400: Endpoint not found., Resource: {service bus endpoint}

until it is restarted.

Repro steps

Internal ticket. Kindly contact @tohling for more information.

Expected behavior

Function should continue to retrieve and process messages from the failed service bus endpoint.

Actual behavior

The Function fails to executed and will continuously throw the following error,

Microsoft.ServiceBus.Messaging.MessagingEntityNotFoundException : 40400: Endpoint not found., Resource:

Known workarounds

Restart the Function.

@tohling
Copy link
Author

tohling commented Nov 28, 2018

@mathewc, @paulbatum - This is more of a feature request to support Geo-DR alias for service bus connection strings.

Based on the documentation, we need to obtain the AliasPrimaryConnectionString through a a new entity known as ServiceBusManagementClient such that the connection string will still work in the event of a failover. Sample code is provided here

https://github.com/Azure/azure-service-bus/blob/master/samples/DotNet/Microsoft.ServiceBus.Messaging/GeoDR/TestGeoDR/ConsoleApp1/Program.cs

@tohling
Copy link
Author

tohling commented Nov 28, 2018

@mathewc - Actually, the customer can provide the correct alias-based connection string upfront in their setup. However, this is a relatively new feature (GA'd in Dec 2017) that is likely not a part of the ServiceBus SDK that V1 is using, so it may just work with the V2 Runtime. We'll need to test this use-case to confirm.

Separately, I have asked the customer to try V2. Will update this thread when I get more information.

@mathewc
Copy link
Member

mathewc commented Nov 28, 2018

Thanks Ling :)

@fabiocav
Copy link
Member

@tohling will you let us know when you have an update on this? Moving this to active questions for now.

@AdiThakker
Copy link

AdiThakker commented Sep 21, 2021

@tohling : Is there any update on this? Should i look anywhere else for more information. Appreciate the feedback. I am currently looking at the Service Bus Extensions sdk and will next look into the functions runtime to see if I can find more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants