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.

Sign up for GitHub

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

Jump to bottom

Broker has file descriptor use spike during reading of manifests that can cause a crash #455

Open
nfachan opened this issue Jan 17, 2025 · 0 comments
Open

Broker has file descriptor use spike during reading of manifests that can cause a crash #455

nfachan opened this issue Jan 17, 2025 · 0 comments
Labels
bug Something isn't working
Milestone
0.13.0

Comments

@nfachan
Copy link
Collaborator

nfachan commented Jan 17, 2025

Specific Maelstrom Program?
maelstrom-broker

Bug Description
Sometimes the broker crashes when kicking off a cargo maelstrom run.

How to Reproduce
Run cargo maelstrom with a large number of jobs. Even if maelstrom-broker doesn't crash, you can see that the file descriptor use spikes by looking in the /proc/<pid>/fd directory.

Expected Behavior
Don't crash.

Additional Context
The issue is most likely that we read the manifests in parallel.
@nfachan nfachan added the bug Something isn't working label Jan 17, 2025
@nfachan nfachan added this to the 0.13.0 milestone Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
0.13.0
Development

No branches or pull requests
1 participant
@nfachan