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

Running several rb.init on same process will hit too many open files error #1646

Closed
frascuchon opened this issue Jul 27, 2022 · 0 comments · Fixed by #1640
Closed

Running several rb.init on same process will hit too many open files error #1646

frascuchon opened this issue Jul 27, 2022 · 0 comments · Fixed by #1640
Assignees
Labels
type: bug Indicates an unexpected problem or unintended behavior
Projects
Milestone

Comments

@frascuchon
Copy link
Member

Describe the bug
Calling several times to rb.init ends by hitting a "Too many open files" error.

To Reproduce
Just run this code:

import rubrix as rb

for i in range(1000):
  rb.init()

Expected behavior
rb.init could be called multiple times without leaking resources.

Screenshots
N/A

Environment (please complete the following information):

  • OS [e.g. iOS]: macOS
  • Browser [e.g. chrome, safari]: N/A
  • Rubrix Version [e.g. 0.10.0]: 0.16.0
  • ElasticSearch Version [e.g. 7.10.2]: N/A
  • Docker Image (optional) [e.g. rubrix:v0.10.0]: N/A

Additional context
N/A

@frascuchon frascuchon added the type: bug Indicates an unexpected problem or unintended behavior label Jul 27, 2022
@frascuchon frascuchon added this to the v0.17.0 milestone Jul 27, 2022
@frascuchon frascuchon self-assigned this Jul 27, 2022
@frascuchon frascuchon added this to Backlog in Release via automation Jul 27, 2022
@frascuchon frascuchon moved this from Backlog to In progress in Release Jul 27, 2022
@frascuchon frascuchon moved this from In progress to Pending Review in Release Jul 28, 2022
Release automation moved this from Pending Review to Waiting Release Aug 2, 2022
@frascuchon frascuchon moved this from Waiting Release to Ready to Release QA in Release Aug 18, 2022
frascuchon added a commit that referenced this issue Aug 18, 2022
frascuchon added a commit that referenced this issue Aug 22, 2022
frascuchon added a commit that referenced this issue Aug 22, 2022
@frascuchon frascuchon moved this from Ready to Release QA to Approved Release QA in Release Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Indicates an unexpected problem or unintended behavior
Projects
No open projects
Release
Approved Release QA
Development

Successfully merging a pull request may close this issue.

1 participant