-
Problem report
-
Resolution: Unresolved
-
Critical
-
7.0.16, 7.2.10
-
None
-
7.2.5+, 7.0.11+
50000+ NVPS, PostgreSQL/TSDB
-
S25-W28/29, S25-W30/31
-
3
Steps to reproduce:
- Configure 11 proxis in 1 proxy group
- Put this proxies correctly in ServerActive parameter o nthe Agent side
- Other settings:
HostMetadata=Linux Telemetry_Release_202502 HostMetadataItem=system.uname
- Run system on high NVPS rate with thousands of Agents
Result:
Get regular deadlocks on auto registration process:
2025-05-05 18:34:14.937 UTC \[3729734] ERROR: deadlock detected
2025-05-05 18:34:14.937 UTC \[3729734] DETAIL: Process 3729734 waits for ShareLock on transaction 1158673410; blocked by process 3751006.
Process 3751006 waits for ShareLock on transaction 1158673399; blocked by process 3729734.
Process 3729734: update autoreg_host set listen_ip='1.2.3.4',listen_dns='vm0',listen_port=10050,host_metadata='Linux Telemetry_Release_202502',tls_accepted='1',flags=0,proxyid=1 where autoreg_hostid=56965;
update autoreg_host set listen_ip='2.3.4.5',listen_dns='vm1',listen_port=10050,host_metadata='Linux Telemetry_Release_202502',tls_accepted='1',flags=0,proxyid=1 where autoreg_hostid=56972;
Process 3751006: update autoreg_host set listen_ip='2.3.4.5',listen_dns='vm1',listen_port=10050,host_metadata='Linux Telemetry_Release_202502',tls_accepted='1',flags=0,proxyid=2 where autoreg_hostid=56972;
update autoreg_host set listen_ip='1.2.3.4',listen_dns='vm0',listen_port=10050,host_metadata='Linux Telemetry_Release_202502',tls_accepted='1',flags=0,proxyid=2 where autoreg_hostid=56965;
At least 2 different proxy_id used for locking SQL:
select proxyid, name, proxy_groupid from proxy where proxyid in (1,2);
proxyid, name, proxy_groupid 1 "proxy5" 1 2 "proxy6" 1
Expected:
No duplicate transactions due to the multiple proxies from one proxy group trying to do auto-registration.
- mentioned in
-
Page Loading...
