Unhandled MPI_Requests generated by mpi_process_group constructor.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- distributed-systems
Research direction
Start with the distributed mpi_process_group constructor and the global_trigger_launcher implementation mentioned in the issue. Reproduce the empty-scope case with MPI request profiling such as LLNL's mpileaks, then trace the non-blocking requests created by the default Irecv configuration. Done means destroying an mpi_process_group leaves no outstanding MPI requests.
Written by the indexing model from the issue text.
Description
The boost::graph::distributed::mpi_process_group class spawns some non-blocking communication in its constructor, but the resulting requests are never handled. I have tracked this down to the global_trigger_launcher, which has the following comment:
// TBD: do not forget to cancel any outstanding Irecv when deleted,
// if we decide to use Irecv
It looks like this was never done, but the default build configuration uses Irecv. To replicate this bug, simply create an mpi_process_group with any constructor, do nothing with it, and let it go out of scope. You will need some way to interact with the MPI profiling interface to detect leaked requests, such as LLNL's mpileaks:
- Dominant language
- C++
- Stars
- 33
- Forks
- 41
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from boostorg/graph_parallel
-
boostorg/graph_parallel#43 · 3 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
boostorg/graph_parallel#39 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
boostorg/graph_parallel#37 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
boostorg/graph_parallel#33 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
boostorg/graph_parallel#27 ·
All issues in boostorg/graph_parallel
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·