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

Fastdds DiscoveryServer Mode Too many open files #5143

Open
1 task done
kaola-zero opened this issue Aug 7, 2024 · 0 comments
Open
1 task done

Fastdds DiscoveryServer Mode Too many open files #5143

kaola-zero opened this issue Aug 7, 2024 · 0 comments
Labels
triage Issue pending classification

Comments

@kaola-zero
Copy link

Is there an already existing issue for this?

  • I have searched the existing issues

Expected behavior

I encountered three problems:
First:
I use FastDDS-2.14.0 version,I used the [Simple Discovery]method and found that establishing 100 publish and subscribe connections takes about 35 seconds, which is a bit long. Is there any way to reduce the time? 5 seconds is ideal, and 10 seconds is acceptable
second:
When I use the discovery server mode in the routine with 100 subscriptions and 100 publishers, the following error occurs: “terminate called after throwing an instance of 'td:: system_ error'
what(): eventfd_select_interrupter: Too many open files
Abandoned (core has been dumped)”, will files always be opened when creating client publish and subscribe? I tried it and found that creating 50 subscriptions requires opening 872 files. Is there a way not to create files?
third:
I increased the number of files that can be opened by changing the system configuration, using the same discovery server mode. However, I found that when the number of published and subscribed files exceeds 50, the connection cannot be established properly.Is there any way to increase the number of connections?
Thank you for any answers!

Current behavior

First:
I use FastDDS-2.14.0 version,I used the [Simple Discovery]method and found that establishing 100 publish and subscribe connections takes about 35 seconds, which is a bit long. Is there any way to reduce the time? 5 seconds is ideal, and 10 seconds is acceptable
second:
When I use the discovery server mode in the routine with 100 subscriptions and 100 publishers, the following error occurs: “terminate called after throwing an instance of 'td:: system_ error'
what(): eventfd_select_interrupter: Too many open files
Abandoned (core has been dumped)”, will files always be opened when creating client publish and subscribe? I tried it and found that creating 50 subscriptions requires opening 872 files. Is there a way not to create files?
third:
I increased the number of files that can be opened by changing the system configuration, using the same discovery server mode. However, I found that when the number of published and subscribed files exceeds 50, the connection cannot be established properly.Is there any way to increase the number of connections?
Thank you for any answers!

Steps to reproduce

Use DiscoveryServerExample build 100 sub or pub

Fast DDS version/commit

Fast-DDS-2.14.0

Platform/Architecture

Ubuntu Focal 20.04 amd64

Transport layer

UDPv4

Additional context

No response

XML configuration file

No response

Relevant log output

No response

Network traffic capture

No response

@kaola-zero kaola-zero added the triage Issue pending classification label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issue pending classification
Projects
None yet
Development

No branches or pull requests

1 participant