On 05/09/2024 16:59, Hugo Mills wrote:
Thanks, both. We're already logging queries, but I was after something
like an API that could give me an instantaneous snapshot of what's
running *right now*, rather than something that I'll have to do post-hoc
analysis on messy log files to get that information. We've used that
capability (through an API endpoint) to good effect in GraphDB, and I
was hoping that there would be something similar in Fuseki.
Thanks,
Hugo.
Hugo,
Sound like a useful addition - maybe done as keeping details of the the
last few 10's queries.
Could you raise a Jena issue for this please?
https://github.com/apache/jena/issues
Andy
Hugo Mills
Development Team Leader
agrimetrics.co.uk <https://www.agrimetrics.co.uk/>
Reading Enterprise Centre, Whiteknights Road, Reading, UK, RG6 6BU
<https://www.linkedin.com/company/agrimetrics/>
<https://x.com/agrimetrics?s=21&t=h8BsEr4MroKUB8051AMAdA>
-----Original Message-----
From: Simon Bin <[email protected]>
Sent: 05 September 2024 15:31
To: [email protected]
Subject: Re: Re: Identifying the currently-running queries
[You don't often get email from [email protected]. Learn
why this is important at https://aka.ms/LearnAboutSenderIdentification ]
In case it is of use, here is our script to parse the Jena 5 logging
output and print the log file in org format, so you can easily browse
the running queries in org-mode:
https://gitlab.com/coypu-project/tools/skynet_loader/-/blob/master/
parse_log49.pl
Note that the logging format changes frequently so it may need small
adjustments in the $date_pattern and the $line regular expression.
Cheers,
On Thu, 2024-09-05 at 16:15 +0200, Lorenz Buehmann wrote:
>
> Hi,
>
> we're running Fuseki 5.1.0 and are using the logging of Jena. That
> works fine for us.
>
> There is no logging of SPARQL Update statements though because those
> can get to large in terms of text.
>
>
>
>
> By the way, I would not run an ancient Fuseki 3.4.0 in production
> anymore - is there a reason for this? just because it works?
>
>
>
>
>
> Cheers,
>
> Lorenz
>
>
> On 05.09.24 14:04, Hugo Mills wrote:
>
>
> >
> >
> > Hi, all,
> >
> >
> >
> > We’ve got a heavily-used webapp backed by Fuseki, and we’re having
> > issues with the load on the Fuseki server. It frequently heads into
> > a storm of high load average, with the CPU usage pegged at 600% (on
> > 6 cores), and then the app grinds to a halt and we have to restart
> > the database. We’re trying to understand why this is happening. Is
> > there the ability in Fuseki to get a list of the currently-running
> > queries at any given point in time, including the query text itself,
> > and preferably also the amount of time each one has been running
> > for?
> >
> >
> >
> > We’re running Fuseki from Jena 3.4.0, if that makes a difference to
> > the answer.
> >
> >
> >
> > Thanks,
> >
> > Hugo.
> >
> >
> >
> >
> >
> > Hugo Mills
> >
> > Development Team Leader
> >
> > agrimetrics.co.uk
> >
> > Reading Enterprise Centre, Whiteknights Road, Reading, UK, RG6 6BU
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
