[
https://issues.apache.org/jira/browse/JENA-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215095#comment-14215095
]
Bala Kolla commented on JENA-703:
---------------------------------
Can you help me experiment with this approach? I would like to see if this
could help us resolve the issue (saturating the system resources, CPU etc..)
mentioned in JENA 801.
> TDB - Ensure readers don't block writeback forever.
> ---------------------------------------------------
>
> Key: JENA-703
> URL: https://issues.apache.org/jira/browse/JENA-703
> Project: Apache Jena
> Issue Type: Improvement
> Components: TDB
> Affects Versions: Jena 2.11.1
> Reporter: Andy Seaborne
>
> The commit queue can only be flushed when the main storage is quiet. A
> stream of readers can lead to the main storage never being quiet.
> One possibility is to place a maximum (quite high) on the number of readers
> allowed after the decision to flush the journal to main storage. If exceeded,
> then lock readers for a while, flush and resume.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
