How can we run a pipeline on a specific node ??
Hi Satish - There are several ways to control which node or Snaplex a pipeline runs on: 1. Pipeline Configuration in Designer When you have a pipeline open in the Designer, you can select the target Snaplex directly from the Snaplex drop-down menu in the pipeline configuration. This determines where the pipeline will run. 2. Scheduled or Triggered Task Configuration When setting up a Scheduled or Triggered Task, you can specify the Snaplex on which the associated pipeline should run during task configuration. 3. Using the Pipeline Execute Snap (for Child Pipelines) When invoking a child pipeline via the Pipeline Execute Snap, you can control node execution using the "Execute On" field, which offers three options: LOCAL_NODE Runs the child pipeline on the same node as the parent pipeline. Best for performance β no network transfer. LOCAL_SNAPLEX Runs the child pipeline on any available node within the same Snaplex as the parent. SNAPLEX_WITH_PATH Runs the child pipeline on a user-specified Snaplex. A Snaplex Path field appears for you to enter the target Snaplex name. Tip: Using LOCAL_NODE is recommended for most child pipeline executions as it avoids network overhead and improves performance. 4. Using pipe.plexPath Expression You can use the pipe.plexPath expression in the Pipeline Execute Snap to dynamically ensure the child pipeline runs on the same node as the parent pipeline. Note: pipe.plexPath is not recommended for Ultra Pipelines, as sending execution to another node can be resource-intensive. 5. Dedicated Snaplex for a Project An Org/Environment admin can assign a dedicated Snaplex to a specific project by moving it from the Shared project to another project. Only pipelines within that project will have access to that Snaplex in Manager and Designer. Best Practices Summary
Use LOCAL_NODE when parent and child pipelines communicate frequently.
Use LOCAL_SNAPLEX when child pipelines handle intensive workloads.
Use SNAPLEX_WITH_PATH only when the child pipeline must run on a different Snaplex due to endpoint connectivity restrictions or workload distribution needs.
Yeah I agree these are the steps to select a specific Snaplex but i want to run on a specific node of a snaplex, is there any way to run on a specific node ?
