[ 
https://issues.apache.org/jira/browse/JENA-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16437354#comment-16437354
 ] 

Andy Seaborne commented on JENA-703:
------------------------------------

This situation does not occur in in TDB2 because write transactions commit as 
they exit and the write updates the main database.

While this is a more expensive scheme, it doesn't have the same issue as this 
ticket.

[~kbkreddy] - is there code from your experiment in 2014?

 

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)

Reply via email to