parisni opened a new issue #19822:
URL: https://github.com/apache/airflow/issues/19822


   ### Official Helm Chart version
   
   1.3.0 (latest released)
   
   ### Apache Airflow version
   
   2.2.1
   
   ### Kubernetes Version
   
   1.2.1
   
   ### Helm Chart configuration
   
   ```yaml
   airflow:
   
     env:
       - name: AIRFLOW__SCHEDULER__USE_ROW_LEVEL_LOCKING
         value: "True"
   
   webserver:
     livenessProbe:
       initialDelaySeconds: 100
       timeoutSeconds: 100
       failureThreshold: 20
       periodSeconds: 25
   
     readinessProbe:
       initialDelaySeconds: 100
       timeoutSeconds: 100
       failureThreshold: 20
       periodSeconds: 25
   
   
   scheduler:
     replicas: 2
   
   executor: CeleryExecutor
   ```
   
   ### Docker Image customisations
   
   _No response_
   
   ### What happened
   
   ```
   duplicate key value violates unique constraint "serialized_dag_pkey"
   DETAIL:  Key (dag_id)=(test_dag_454) already exists.    
    scheduler [SQL: INSERT INTO serialized_dag (dag_id, fileloc, fileloc_hash, 
data, last_updated, dag_hash) VALUES (%(dag_id)s, %(fileloc)s, 
%(fileloc_hash)s, scheduler [parameters: {'dag_id': 'test_dag_454', 'fileloc': 
'/opt/airflow/dags/repo/test_dag_454.py', 'fileloc_hash': 14390114031793844, 
'data': '{"__vers  scheduler (Background on this error at: 
http://sqlalche.me/e/13/gkpj)
   ```
   
   ### What you expected to happen
   
   _No response_
   
   ### How to reproduce
   
   _No response_
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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