Skip to content

connect: fix connection timeout#108

Closed
sssciel wants to merge 1 commit into
masterfrom
g.rybakov/tntp-7780-connect-timeout
Closed

connect: fix connection timeout#108
sssciel wants to merge 1 commit into
masterfrom
g.rybakov/tntp-7780-connect-timeout

Conversation

@sssciel
Copy link
Copy Markdown
Member

@sssciel sssciel commented May 27, 2026

NewEtcdStorage checked the cluster status through the Maintenance.Status function, which requires root permissions. Replace it with MemberList (serializable), which is open to any authenticated user and avoids a raft round-trip, so the connection probe no longer crashes for non-admin credentials.

Part of TNTP-7780

@sssciel sssciel force-pushed the g.rybakov/tntp-7780-connect-timeout branch from eb35a20 to ed09c1a Compare May 27, 2026 17:50
Right now, NewStorage uses one common timeout for both connections. At
the same time, it uses the same timeout as the main one to attempt a
connection. It turns out that when connecting to the second tcs
storage, the time may have already run out, which leads to a drop in
connection. Now the connections have different timeouts.

Part of TNTP-7780
@sssciel sssciel force-pushed the g.rybakov/tntp-7780-connect-timeout branch from ed09c1a to dc750cf Compare May 27, 2026 17:50
@sssciel sssciel closed this May 27, 2026
@sssciel sssciel deleted the g.rybakov/tntp-7780-connect-timeout branch May 27, 2026 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant