python3-pysyncobj package stuck on jammy on primary raft re-election due to dead TCP

[Alex Lutay]

Hi,

Data Team is experiencing a stability issue with PostgreSQL Primary lost due to lack of Raft Primary election (based on python3-pysyncobj 0.3.10 from Jammy).

The issue has been traced by upstream and fixed in 0.3.12 (available in Nobel):
https://github.com/bakwc/PySyncObj/issues/172
> #172 Added tcp keepalive - fixed bug when cluster was unable to select a new leader due to stuck tcp connection

It is a ticket to request Jammy library patchset version update 0.3.10->0.3.12 (prefered)
OR PPA/backport creation for Jammy.

P.S. Data Team reference: https://warthogs.atlassian.net/browse/DPE-3684
 PySyncObj release notes: https://github.com/bakwc/PySyncObj/releases

[Lena Voytek (lvoytek)]

Added 0.3.12 to the data platforms ppa for jammy. Here is a PPA containing the upstream tcp keepalive fix as a patch for mantic and jammy - https://launchpad.net/~lvoytek/+archive/ubuntu/pysynconj-tcp-keepalive
I can at least add this to the previous versions via an SRU if it fixes the issue.

[Alex Lutay (taurus)]

Thank you Lena, copy here the yesterday's discussion for the history:

The PR#172 might be not enough... https://github.com/bakwc/PySyncObj/pull/163 smells related as well.
We decided to go with version 0.3.12 as Jammy PPA https://launchpad.net/~data-platform/+archive/ubuntu/python-pysyncobj

Thank you for the quick build here!