[NIFI-11261] GetAzureEventHub does not disconnect on Primary Node Changes

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.20.0
• Fix Version/s: 2.0.0-M1, 1.21.0
• Component/s: Extensions
• Assignee: David Handermann
• Reporter: David Handermann
• Created: 08/Mar/23 18:25
• Updated: 09/Mar/23 21:51
• Resolved: 09/Mar/23 21:51

Description

The GetAzureEventHub Processor creates an Event Hub Client when scheduled and maintains the client instance until Processor is stopped. This approach works for standalone deployments, but is not suitable for clustered deployments because the client maintains connections after the primary node changes.

The ConsumeAzureEventHub Processor provides the preferred approach for consuming events, but GetAzureEventHub should be updated to handle primary node state changes.

Issue Links

• links to: GitHub Pull Request #7023