potiuk commented on issue #28380:
URL: https://github.com/apache/airflow/issues/28380#issuecomment-1355537151

   > @potiuk, I still have the issue. Nevertheless, monkey patch warning have 
disappeared.
   
   This is a good news. At least it allows us to merge this change because 
clearly the warnings are removed.
   
   > I am quite sure now that the celery broker or backend are responsible. The 
result backend database are not updated when some tasks finished, contrary to 
metadata database...
   
   > What do you think?
   
   There are many things that could have caused the behaviour  - but without 
any evidences, I can only guess, and I have no prior similar experience to base 
it on. As discussed on Slack the "Celery" Executor is not supported in Breeze 
as a "working" feature (Issue opened 
https://github.com/apache/airflow/issues/28412 . It might well be some issue in 
the way how things are configured in Breeze. If you would like to explore it 
further and try to investigate how to implement it, that woudl be awesome. But 
this is not a high priority, really and I would prefer someone (like you) who 
is a celery user can do some more investigation how to make it works in Breeze. 
This happend in the past and I would like more of the contirbutors to spend 
their time in improving our dev env - seems that someone who understand what 
gevent is and wants to use it has enough incentive to do more investigation. 
Happy to help with it but need more evidences and some deeper debugging from 
your side if we are to pr
 ogress there.
   
   I am happy to get ideas bounced off me and to help to understand ins-outs of 
Breeze to guide such a person. Slack discussion in #breeze  channel on slack is 
likely best place for that.
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to