Kaxil Naik
Kaxil Naik
My 2 cents: For AF 3: Would move the callbacks and stuff to the workers or separate components For Option (2): How much less work is it? :)
> I think we should support both 1.4 and 2.0 for at least one minor release, preferrably much longer. Dependencies don’t tend to catch up very fast for this kind...
> We were able to improve the behavior with these settings: > > ``` > AIRFLOW__CELERY_BROKER_TRANSPORT_OPTIONS__SOCKET_TIMEOUT=30 > AIRFLOW__CELERY_BROKER_TRANSPORT_OPTIONS__SOCKET_CONNECT_TIMEOUT=5 > AIRFLOW__CELERY_BROKER_TRANSPORT_OPTIONS__SOCKET_KEEPALIVE=True > AIRFLOW__CELERY_BROKER_TRANSPORT_OPTIONS__RETRY_ON_TIMEOUT=True > ``` > > In our repro (which...
@dimberman Can you get this to the finish line please?
If this was in a release, we should not remove it until 2.0
Is it still the case @utkarsharma2 ?
>Is there any way to do that? Not currently, but feel free to raise a PR -- shouldn't be difficult.
Why this in review state since 5 days?
@tatiana Any progress on this one?
cc @bolkedebruin I haven't looked at the code, but was expecting that during deserialization this works out of the box. https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/xcoms.html#object-storage-xcom-backend