[Mulgara-dev] Monitoring resource use

[Life is hard, and then you die]

On Sun, Nov 09, 2008 at 03:33:48PM -0600, Paul Gearon wrote:
> On Fri, Nov 7, 2008 at 8:40 PM, Life is hard, and then you die
> <ronald at innovation.ch> wrote:
> > On Fri, Nov 07, 2008 at 05:37:49PM -0500, Alex Hall wrote:
> >> Does anybody have any insight into the topic of monitoring resource
> >> usage of a Mulgara server?  The idea is, once we put up a publicly
> >> available, Mulgara-backed website that incorporates the ability to
> >> execute SPARQL queries, we expose ourselves to denial-of-service
> >> attacks.  The sort of thing that I would be interested in doing is
> >> some sort of throttling or rate control; assigning different
> >> priorities to queries; and monitoring queries to either kill or
> >> lower the priority of ones that are running too long.  One possible
> >> approach would be to extend MBean capability to the Session level
> >> (right now there is an MBean interface for the server object) but
> >> I'm sure there are others.  I'd love to hear back from anybody with
> >> experience or thoughts on this topic.
> 
> Yes, the current MBean isn't all that informative, and I don't think
> it lets you do any control at all (does it?).
> 
> > Right we just monitor by looking at os stats such as cpu and memory
> > used; more JMX support would be really great, though (there is the
> > ServerMBean, but it's not actually exported as an MBean).
> 
> What do you mean by this? Standard MBeans don't require anything
> except to meet the naming conventions. Are you talking about something
> the server needed to do?

Um, no, that's not quite true: you need to register your MBeans with
the MBean server for them to be visible. So yes, mulgara needs to
register them. Right now if you enable jmx and fire up jconsole you'll
see that there's nothing there except the default MBeans (e.g. for
java.util.logging).


  Cheers,

  Ronald