On Fri, May 11, 2012 at 12:18 AM, Jan Friesse <jfriesse@xxxxxxxxxx> wrote: > Andrew Beekhof napsal(a): > >> On Fri, Apr 13, 2012 at 7:07 PM, Jan Friesse<jfriesse@xxxxxxxxxx> wrote: >>> >>> I invite all of our contributors to help define the X.Y roadmap of >>> Corosync. >>> Please submit your ideas on this list. Some >>> examples of suggested ideas have been things like "remove binding to >>> localhost", "don't rely on multicast loop facility" or "include user data >>> in >>> cpg join/callbacks". >>> >>> Please submit your ideas by May 11, 2012 (Friday). >> >> >> Could we do something about the logging? >> > > Andrew, > I agree with you that delivered msg is really not very interesting in most > cases. > > Do you mean something like DEBUG2 (in libqb there is LOG_TRACE with this > meaning)? Switching it to equivalent of LOG_TRACE sounds like a great idea to me. > Honza > > >> I have a couple of bugs filed already but in addition it would be nice >> to have a usable debug mode. >> The problem right now is that when enabled the logs fill up with >> >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] mcasted message >> added to pending queue >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] Delivering da to dc >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] Delivering MCAST >> message with seq db to pending delivery queue >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] Delivering MCAST >> message with seq dc to pending delivery queue >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] Received >> ringid(192.168.122.101:6696) seq db >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] Received >> ringid(192.168.122.101:6696) seq dc >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] Received >> ringid(192.168.122.101:6696) seq dd >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] Delivering dc to dd >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] Delivering MCAST >> message with seq dd to pending delivery queue >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] Received >> ringid(192.168.122.101:6696) seq de >> Apr 15 18:42:29 pcmk-1 corosync[4913]: [TOTEM ] Delivering dd to de >> >> which redundantly redundant, not terribly informative and so verbose >> that syslog ends up dropping most of corosync's logs anyway: >> >> Apr 15 18:42:29 pcmk-1 rsyslogd-2177: imuxsock lost 644 messages from >> pid 4913 due to rate-limiting >> Apr 15 18:42:35 pcmk-1 rsyslogd-2177: imuxsock lost 664 messages from >> pid 4913 due to rate-limiting >> >> 600+ messages being thrown away at a time is pretty bad. >> Adding in the messages that /did/ make it to the logs between the two >> times, corosync is pumping out messages at more than 390 per _second_. > > _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
