aio-libs / aio-libs/aiopg

handle Invalid transaction status on released connection

未關閉
#495 4 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
Python
星號
1.4k
分支
170
PR 合併指標
30 天內沒有已合併 PR

描述

How to handle server down unexpectly?
Test system is two nodes with haproxy+keepalived on VBox.
Testscript is write 10k values on 10 workers.
When terminal machine is down
```
Invalid transaction status on released connection: 1
Invalid transaction status on released connection: 1
Invalid transaction status on released connection: 1
Invalid transaction status on released connection: 1
Invalid transaction status on released connection: 1
Invalid transaction status on released connection: 1

```
How i can handle it?

貢獻指南

開啟貢獻指南

研究方向

No source file or test is named. Start by reproducing the two-node HAProxy and keepalived setup described in the report, with 10 workers writing 10k values while a terminal machine goes down, then trace where the released connection reports transaction status 1. Done should be a documented and tested handling for this failure case.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
postgresql, python, sqlalchemy
領域
databases
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。