Hi Håvard,
I'm glad to hear that Fuseki been useful to you for several years.
What you report is quite bizarre. A difference between Fuseki2 and
Fuseki1 is the version of Jetty being used (Jetty9 vs Jetty8). Jetty8
has been reported to lock up under some conditions, though not Java8
specifically nor in the way you are using it. I don't know the exact
cause there (or it would be fixed!) but something in the area of
connection management+the connector choice might be related.
Jetty9 is very different to Jetty8 in it's networ khandling.
So my only guess is that the combination of Java8 and Jetty8 have pushed
it into a bad place.
Fuseki2 should be compatible with Fuseki1.
Please do let us know if continues to keep running properly.
Andy
On 07/05/15 09:32, Håvard Ottestad wrote:
Hi,
TLDR; Fuseki 1.x hangs every 5 hours, Fuseki 2 is fine. Might be a problem with
Java.
We’ve been running Fuseki for many years here at POSC Caesar Association and
been very happy with it.
Recently we have had massive slow downs, that have resulted in us having to
restart Fuseki. We run:
Fuseki 1.0.1 and 1.1.2 in Docker with Oracle Java 8 on Ubuntu. We use the
in-mem database.
Our experience has been that, with a continues flow of queries (1 every 30
seconds) Fuseki will stop responding for more than 30 minutes very ~5 hours.
Even during the night, when there are no queries running except for the ones
that we use to monitor Fuseki (select 12 triples).
I have tried:
- Reduce number of queries
- Increase ram to 4x (2GB)
- Updated from 1.0.1 to 1.1.2
- Removed all complex queries
- Changed to G1 GC
Now I have upgraded to Fuseki 2. Which is the only solution that is holding.
We’ve had 12 hours without any issues :)
If anyone wants to diagnose these issues further I can provide more information
about our setup (including our data).
Cheers,
Håvard M. Ottestad
PCA Services (a part of POSC Caesar Association)
