Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect fails to slow providers #2329

Closed
zolia opened this issue Jun 3, 2020 · 3 comments
Closed

Connect fails to slow providers #2329

zolia opened this issue Jun 3, 2020 · 3 comments
Assignees

Comments

@zolia
Copy link
Contributor

zolia commented Jun 3, 2020

looks like #2312 introduced another problem when connecting to slow providers fails prematurely. Sometimes connect to node takes ~30sec. I know this is unreasonably long, but probably we should allow such duration to take place. To solve issue for connect hanging forever we could set 2min or so dial timeout.

Also some progress feedback for a users on applications would be great. We could have some progress bar reflecting stages that were reached for given session in progress.

@soffokl
Copy link
Member

soffokl commented Jun 3, 2020

@zolia Could you list such providers? I'd like to check why this is so slow.

@zolia
Copy link
Contributor Author

zolia commented Jun 3, 2020

Most likely not this one timeout hits, but 20 sec timeout on dial while sending / awaiting statues in sendSessionStatus() Can reproduce it only with mobile client so far.
You can use this RPI to test: 0x2bc8193504a60c1d9746006a9eb3ade5d6b7f51b

@anjmao
Copy link
Contributor

anjmao commented Jun 8, 2020

For now I added connection traces which can be used to determine individual slow parts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants