<div dir="ltr">Maybe it would be appropriate for M/R tasks, which can be expected to be slow anyway. But I'd rather have a progress reporting/statistics interface, so that the application can decide for itself whether it's worth logging something as INFO or as DEBUG.<div>
<br></div><div>I would expect queries to be not just fast, but also numerous, so I wouldn't log anything above TRACE for individual queries.</div><div><br></div><div>Cheers</div><div>Dan<br><div class="gmail_extra"><br>
</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 12, 2014 at 5:01 PM, Alan Field <span dir="ltr"><<a href="mailto:afield@redhat.com" target="_blank">afield@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div style="font-family:times new roman,new york,times,serif;font-size:12pt;color:#000000"><div>Hey Dan,<br></div><div><br></div><div>I know there aren't too many messages today, but I was thinking that status and statistics messages would be good to show. (Map/Reduce task ID ### has started the map phase, Map/Reduce task ID ### has completed the map phase + stats, etc., Query ID ### executed in x.xx secs)</div>
<div><br></div><div>Thanks,</div><div>Alan</div><div><br></div><hr><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">
<b>From: </b>"Dan Berindei" <<a href="mailto:dan.berindei@gmail.com" target="_blank">dan.berindei@gmail.com</a>><div class=""><br><b>To: </b>"infinispan -Dev List" <<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a>><br>
</div><b>Sent: </b>Tuesday, August 12, 2014 2:37:45 PM<br><b>Subject: </b>Re: [infinispan-dev] Log message categories<div><div class="h5"><br><div><br></div><div dir="ltr">I don't think we have a lot of INFO map/reduce or dist exec, but perhaps some DEBUG messages' level could be increased. Actually, that is also true for state transfer and rebalancing messages...<div>
<br></div><div>I agree in principle with the idea, my only concern is that we'll spend too much time managing which messages should be moved to these special categories (and sometimes moved from DEBUG to INFO).</div>
<div>
<br></div><div>Cheers</div><div>Dan</div><div><br></div></div><div class="gmail_extra"><br><div><br></div><div class="gmail_quote">On Tue, Aug 12, 2014 at 3:20 PM, Alan Field <span dir="ltr"><<a href="mailto:afield@redhat.com" target="_blank">afield@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I would also propose these categories for log messages:<br>
<br>
org.infinispan.QUERY<br>
org.infinispan.MAPREDUCE<br>
org.infinispan.DISTEXEC<br>
<br>
Thanks,<br>
Alan<br>
<div><div><br>
----- Original Message -----<br>
> From: "Tristan Tarrant" <<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a>><br>
> To: "infinispan -Dev List" <<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a>><br>
> Sent: Tuesday, August 12, 2014 10:35:34 AM<br>
> Subject: [infinispan-dev] Log message categories<br>
><br>
> Dear all,<br>
><br>
> currently the Infinispan log messages "fall" in the categories named<br>
> from the originating class. While this isfine for TRACE/DEBUG messages,<br>
> there are some high-level INFO events which warrant their own specific<br>
> categories. I think that user-triggered events (such as JMX ops) should<br>
> also be treated like this.<br>
> Examples:<br>
><br>
> org.infinispan.CLUSTER (for important view change, state transfer and<br>
> rebalancing messages)<br>
> org.infinispan.CACHE (for cache lifecycle events)<br>
> org.infinispan.PERSISTENCE<br>
><br>
> What do you think ?<br>
> Any other suggestions ?<br>
><br>
> Tristan<br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div>
<br>_______________________________________________<br>infinispan-dev mailing list<br><a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a></div>
</div></blockquote><div><br></div></div></div><br>_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br></blockquote></div><br></div></div></div>