You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/10/06 12:34:00 UTC

[GitHub] [airflow] asd855280 commented on issue #25750: Metadata DB lock wait timeout exceeded when delete from xcom table(airflow 2.1.0)

asd855280 commented on issue #25750:
URL: https://github.com/apache/airflow/issues/25750#issuecomment-1269959595

   > I think this is some of the cleanup which is run by you. Airflow never deletes Xcom on its own. Likely you are using DAG cleanups from a 3rd-party. I recommend to switch to latest Airflow version and rather than relying on 3rd-party cleanups use periodically run `airflow db clean` CLI that was added in 2.3.3.
   
   Hi thanks, and sorry for the late reply, 
   We are not using any 3rd-party cleanup tool, we installed pure open source airflow 2.1.0 version.
   
   We found out that the xcom table in metadata db did not consist of any index, we were wondering would it be possible that when multiple workers and schedulers are manipulating data on xcom table, the execution takes longer because of lacking of index.  


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org