I don’t have a strong opinion either way (and I’m not on the PMC so take my thoughts with a grain of salt), but I do see a tradeoff with both approaches.
The existing approach has the obvious downside of not balancing the load across the cluster. I can understand the appeal of alleviating that, as it’s something I’ve occasionally considered in my own environment. However, switching to a load balanced approach has a downside as well. Troubleshooting becomes more difficult. Today, I can log into a cluster, check which node is primary, and know where to expect those processors to be executing. This has been useful, on rare occasions. As I said, I don’t have a particularly strong opinion, but I’d be curious if others have also benefitted from knowing where a given processor was executing. Perhaps, there would be a way to indicate to users where the cluster thinks a given single-node processor is supposed to be scheduled..? From: Mark Payne <[email protected]> Date: Wednesday, March 4, 2026 at 15:09 To: [email protected] <[email protected]> Subject: [DISCUSS] NIP - Single Node Only Execution Node This Message Is From a New Sender You have not recently corresponded with this sender. If this is someone you frequently correspond with, confirm with them directly they sent this email message from a new email address. For more resources, visit security.cat.com/phishing. Hi team, I just filed a new NIP [1] to discuss a proposal for introducing a new Single Node Only value for the Execution Node. Rather than having all “Primary Node Only” processors run on a given node, this would allow us to spread the load over all nodes in the cluster. I look forward to any discussion on the proposal. Thanks -Mark [1] https://urldefense.com/v3/__https://issues.apache.org/jira/browse/NIP-22__;!!FtR4BK4x7WL3xYs!4bm91eUMT8pKjFpP_WTDzhdlyWsc32BlWQGntfWtqCGjvRLPvP7D_tBxS-q_NlLDC-oy-5_gA_MH-yVXaA$
