`@rapidsai/sql` SQLCluster UCX comms broken after switch to static linking
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 211
- Forks
- 29
- Avg merge
- 17h 30m
- Merged PRs (30d)
- 1
Description
Seems like UCX behaves differently when applications statically link cudart, and that different behavior may be affecting blazingsql's comms. Filing an issue to investigate this.
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.
Research direction
The issue names no files, tests, or entry points. Investigate the @rapidsai/sql SQLCluster communication path and compare UCX behavior before and after static cudart linking. Done means identifying the cause of the broken communications and documenting or implementing a verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, sql, typescript
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100