Skip to content

feat(processing_engine): Attach a node id to the processing engine and triggers for multi-node support compatibility.#26136

Merged
jacksonrnewhouse merged 1 commit intomainfrom
processing_engine/node_id
Mar 13, 2025
Merged

feat(processing_engine): Attach a node id to the processing engine and triggers for multi-node support compatibility.#26136
jacksonrnewhouse merged 1 commit intomainfrom
processing_engine/node_id

Conversation

@jacksonrnewhouse
Copy link

In the Enterprise version triggers will be tied to a specific node. This change ensures a smooth upgrade path from Core to Enterprise.

…d triggers for multi-node support compatibility.
@jacksonrnewhouse jacksonrnewhouse merged commit 331f885 into main Mar 13, 2025
12 checks passed
Comment on lines +382 to +388
if trigger.node_id != self.node_id {
error!(
"Not running trigger {}, as it is configured for node id {}. Multi-node not supported in core, so this shouldn't happen.",
trigger_name, trigger.node_id
);
return Ok(());
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I see this may be a place where a ProcessingEngineManager trait could be useful. Perhaps my removing that was pre-emptive...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants