Thanks Matt, I'll silence it then. Cheers, Damien
On Mon, Jun 1, 2015, at 05:44 PM, Matt Brender wrote: > > Hey Damien, > > I followed up internally and had Brian Sparrow share the details: > > This is just saying that an operation took longer than a configurable > threshold. It can safely be ignored. I believe the default threshold > is 1ms. Looks like this was disabled in earlier versions but was re- > enabled in vm settings in 2.1. > > _ > http://erldocs.com/current/erts/erlang.html?i=2&search=system_mon#system_monitor/2_ > > Cheers, Matt > > > -- > Matt Brender | Developer Advocacy Lead > [t]@mjbrender[1] > > On Wednesday, May 27, 2015 at 11:26 AM, Damien Krotkine > <dkrotk...@gmail.com>, wrote: >> Hi, >> >> >> >> In a cluster with 27 nodes, running 2.0.0, I upgraded one node >> to 2.1.1 >> >> (riak-2.1.1-1.el6.x86_64.rpm). Since them, this node is >> producing these >> >> kind of logs, every couple of minutes: >> >> >> >> 2015-05-27 14:56:31.978 [info] >> >> <.94.0>@riak_core_sysmon_handler:handle_event:92 monitor >> long_schedule >> >> <.1201.0> >> >> [{initial_call,{riak_core_vnode,init,1}},{almost_current_function,{g- >> en,do_call,4}},{message_queue_len,1}] >> >> [{timeout,1329},{in,{gen,do_call,4}},{out,{gen,do_call,4}}] >> >> >> >> >> >> Any idea what this is and if it's harmful? I'd like to double check >> >> before upgrading the other nodes >> >> >> >> Thanks >> >> dams. >> >> >> >> _______________________________________________ >> >> riak-users mailing list >> >> riak-users@lists.basho.com >> >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > Links: 1. http://twitter.com/mjbrender
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
