Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
restart eBPF tracking on error #2735
This is a workaround for #2650
Tested manually the following way:
Start Scope with:
Simulate EbpfTracker failure with:
I updated the code. It seems to restart fine. But I had one instance of my test where Scope was talking 100% of the cpu in the gobpf code when I tested the fallback to proc parsing.
I got the stack of the go routine taking all the cpu with the following command. The stack changes all the time since it is running.
Also, the integration test needs fixing too: https://circleci.com/gh/kinvolk/scope/990
changed the title from
[WIP] restart eBPF tracking on error
restart eBPF tracking on error
Jul 25, 2017
It seemed to work fine.
But then, I had a look at the go routine stacks with pprof after Scope fell back on proc parsing:
Fix in gobpf, tested on GCE: https://gist.github.com/alban/cb4b899e9558e231d080ec7e7b3abbc5
It seems to resolve the leaking go routine.