d4dbdfb61d
### What problem does this PR solve? If you deploy Ragflow using Kubernetes, the hostname will change during a rolling update. This causes the consumer name of the task executor to change, making it impossible to schedule tasks that were previously in a pending state. To address this, I introduced a recovery task that scans these pending messages and re-publishes them, allowing the tasks to continue being processed. ### Type of change - [ ] Bug Fix (non-breaking change which fixes an issue) - [x] New Feature (non-breaking change which adds functionality) - [ ] Documentation Update - [ ] Refactoring - [ ] Performance Improvement - [ ] Other (please describe): --------- Co-authored-by: liuzhenghua-jk <liuzhenghua-jk@360shuke.com> |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| azure_sas_conn.py | ||
| azure_spn_conn.py | ||
| doc_store_conn.py | ||
| es_conn.py | ||
| infinity_conn.py | ||
| minio_conn.py | ||
| oss_conn.py | ||
| redis_conn.py | ||
| s3_conn.py | ||
| storage_factory.py | ||
| tavily_conn.py | ||