[Twisted-Python] carbon-relay eating CPU - EAGAIN (Resource temporarily unavailable)?

Phil Mayers p.mayers at imperial.ac.uk
Tue Nov 26 04:51:40 MST 2013


On 26/11/13 04:05, Quan Tong Anh wrote:
>   - Python 2.7.3
>   - [twisted, version 13.1.0]
>   - xen-domU

I assume xen-domU means "Linux" as the guest OS; which kernel version, 
out of interest.

>
> `atop` shows that `carbon-relay` is eating 80, 90% USRCPU. From the

I don't know about anyone else, but I don't know what carbon-relay is. A 
quick google suggests it's part of that graphite monitoring/RRD 
replacement thing; which version are you running (Or: what reactor is it 
using)?

How many open files do you have?


> `strace`:

Without timestamps it's difficult to interpret this unambiguously; that 
could be a microsecond or minute we're seeing ;o)

> The strange thing is: even restart the service, it seems stuck at fd 7
> everytime running `strace`. Does it mean this fd is not being cleanup
> properly?

No. fd numbers are allocated starting from 0 and going upwards. The same 
process running the same startup code every time will tend (not always, 
since it's order-dependent) to use the same file descriptors for the 
same things, modulo close/open events.




More information about the Twisted-Python mailing list