llnl / llnl/UnifyFS

slow client can make unifyfsd assert

Open
#668 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
122
Forks
34
PR merge metrics
No merged PRs in 30d

Description

### System information

Type | Version/Name
--- | ---
Operating System | Linux
OS Version | Ubuntu 20.04.2
Architecture | x86_64
UnifyFS Version | git (115e5be54b5)

### Describe the problem you're observing

unifyfsd can hit a margo assertion:

```
[critical] unexpected return code (11: HG_INVALID_ARG) from HG_Progress()
unifyfsd: ../src/margo-core.c:1488: __margo_hg_progress_fn: Assertion `0' failed.
2021-08-12T15:32:17 tid=1387996 @ unifyfs_heartbeat_rpc() [margo_client.c:895] responding
```

### Describe how to reproduce the problem

hook up a debugger to a UNIFY client and slowly walk through the code

### Include any warning or errors or releveant debugging data

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the assertion while slowly stepping through a UNIFY client under a debugger. Trace unifyfs_heartbeat_rpc() at margo_client.c:895 and the reported failure in __margo_hg_progress_fn at src/margo-core.c:1488. Done means a slow client no longer causes unifyfsd to assert on HG_Progress().

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
distributed-systems, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.