[NIFI-3155] Remote Group Port UUIDs

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Matt Gilman
• Created: 06/Dec/16 02:06
• Updated: 12/Feb/18 22:57
• Resolved: 13/Nov/17 19:13

Description

Remote Group Ports assume the UUID of the port on the target instance. This is critical for retaining which port the connection is associated with. However, this is problematic for any flow which contains multiple RPGs pointed to the same target instance. Associating the underlying component when only an ID is known (ie provenance) is impossible as the UUID is ambiguous.

This issue also exists for self-referencing RPGs but is mitigated with extra logic around these troublesome scenarios. For instance, we can differentiate the Remote Group Port from the Root Group Port of a self-referencing RPG by looking at the component type. However, this isn't possible with multiple RPGs referencing the same target instance.

Issue Links

• incorporates: NIFI-4874 RPGs to flows that share the same flow and port UUIDs can cause non-deterministic FlowFile transmission
• relates to: NIFI-4571 Multiple Remote Process Groups that point to same URL show the same stats
• links to: GitHub Pull Request #2253