edgexfoundry / edgexfoundry/device-sdk-c
Skip AutoEvents if they are taking too long
Open
- Dominant language
- C
- Stars
- 45
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
If an AutoEvent is scheduled to run, and the previous invocation is still running, log an error and skip the new run.
The current implementation continues to spawn new threads into the get_handler, which is likely to worsen the situation on an overloaded machine.
Contributor guide
Research direction
Start by tracing the AutoEvent scheduling path into get_handler and identify where a new thread is spawned while the previous invocation is still running. Verify the behavior on an overloaded machine, then confirm that the overlapping run is logged as an error and skipped rather than creating another thread.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100