> > *IMPORTANT NOTE*: task instances that run on the default/environment > executor (i.e. with no specific override provided) will not persist the > executor in the same way so that they can be re-run/retried on any executor.
Does this mean that any task that doesn't have the `executor` parameter specified will run on the default executor for its first attempt, but any executor on subsequent attempts? If so, how will users specify the default executor? Also, I think this will provide some debugging challenges when a task runs on one executor on one attempt, but a different executor on a different attempt. It might be nice if users could set a `use_default_executor_on_retry` kind of parameter. On Mon, Jan 15, 2024 at 1:05 PM Oliveira, Niko <oniko...@amazon.com.invalid> wrote: > Hey folks! > > I'd like to announce a new proposal for Airflow. I've teased this before > in my talk on executors at this year's summit and it was also mentioned in > the townhall last week. > > It's a proposal to allow using multiple executors concurrently within a > single Airflow environment. > > > Let me know what you think! > > https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-61+Hybrid+Execution > > Cheers, > Niko >
