Hi Dan,
On 20/09/2024 15:18, Dan Pritts wrote:
Sorry for the late reply
We identified a problem with a similar old fuseki version. Using the
internal backup mechanism caused fuseki to slow down drastically and
take down our website, usually ending in us restarting.
Which version?
And is i
Sorry for the late reply
We identified a problem with a similar old fuseki version. Using the
internal backup mechanism caused fuseki to slow down drastically and take
down our website, usually ending in us restarting.
We disabled the fuseki internal backups and instead make Linux lvm
snapshots o
w.linkedin.com/company/agrimetrics/>
<https://x.com/agrimetrics?s=21&t=h8BsEr4MroKUB8051AMAdA>
-Original Message-
From: Simon Bin
Sent: 05 September 2024 15:31
To: users@jena.apache.org
Subject: Re: Re: Identifying the currently-running queries
[You don't often get email
From: Simon Bin
Sent: 05 September 2024 15:31
To: users@jena.apache.org
Subject: Re: Re: Identifying the currently-running queries
[You don't often get email from s...@informatik.uni-leipzig.de. Learn why this
is important at https://aka.ms/LearnAboutSenderIdentification ]
In case it is o
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 freque
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 f
