Interesting. I only ran into this issue once, but I remember what I was doing. So I'll try to reproduce it later tonight, and if I succeed I'll send you more info -- to eventually pass on to the Erlang folks.
Thanks, Francisco 2010/11/29 David Smith <[email protected]>: > Thanks for the info. > > A more careful reading of EAGAIN related messages says that: > > "A temporary resource shortage made an operation impossible. fork can > return this error. It indicates that the shortage is expected to pass, > so your program can try the call again later and it may succeed. It is > probably a good idea to delay for a few seconds before trying it > again, to allow time for other processes to release scarce resources. > Such shortages are usually fairly serious and affect the whole system, > so usually an interactive program should report the error to the user > and return to its command loop." > > It looks, from the logs, like memsup was a bit aggressive in retrying > that call and consequently exceeded the supervisor restart frequency; > eventually this percolated up the supervisor chain and the VM was > taken down (as it should be). > > That is to say, I don't see anything here that we can fix via Riak -- > it appears (based strictly on the available data) to be something > inside the Erlang/OTP distribution. Can you easily reproduce this > issue? > > Thanks, > > D. > _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
