[
https://issues.apache.org/jira/browse/JENA-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884796#comment-15884796
]
Andy Seaborne commented on JENA-1296:
-------------------------------------
FYI:
TDB2 does not have the same need as TDB1 for keeping stuff in the journal after
the write transaction commits. All work is done during the transaction.
So it does not have the effect as TDB1 where a high load can cause there to be
a build up of pending finalization work in the journal.
> Fuseki SPARQL endpoints become permanently unresponsive after read/write load
> -----------------------------------------------------------------------------
>
> Key: JENA-1296
> URL: https://issues.apache.org/jira/browse/JENA-1296
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki, TDB
> Affects Versions: Fuseki 2.4.1, Fuseki 2.5.0
> Environment: CentOS 7.3 inside VM, 2 cores, OpenJDK 1.8.0_121
> (64-bit), 1GB JVM heap, Fuseki running as service
> Reporter: Vilnis Termanis (Iotic Labs)
> Priority: Critical
> Attachments: fuseki_lockup.tgz, threaddump-1487963000778.tdump
>
>
> *Steps:*
> # Start with plain Fuseki + given configuration (simple TDB store)
> # Import 1k.ttl
> # Run lockup.py (same host, mix of multiple parallel updates & single select)
> *Result:*
> After some time Fuseki stops accepting any additional SPARQL queries until it
> is restarted. (They time out at client end and are left in CLOSE_WAIT state
> on server). During my testing this happened within ~30s of running the script.
> *Notes:*
> - Locks up more quickly if JVM has had cold start (e.g. restart after step 2)
> but it definitely is *not* only a startup issue.
> - During testing the VM was very rarely I/O limited.
> - The "static" web UI elements are accessible, but any SPARQL-querying
> features (e.g. triple count) do not
> - Reproducible as detailed above in v2.4.1 & v2.5.0
> - In v2.4.0 and v2.3.1 no lockup seems to occur, but once the script has been
> running for a while, the SELECT query times out sometimes.
> So for now we're limited to using the (now somewhat old) v2.3.1 - it would be
> nice to be able to upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
