[
https://issues.apache.org/jira/browse/JENA-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433031#comment-15433031
]
ASF subversion and git services commented on JENA-1224:
-------------------------------------------------------
Commit 166b6e9ccf1b4d4b0b93b49444a2534a083c09c4 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=166b6e9 ]
JENA-1224: Flush based on trying to keep below a max size.
> Limit the number of outstanding write transactions in TDB.
> ----------------------------------------------------------
>
> Key: JENA-1224
> URL: https://issues.apache.org/jira/browse/JENA-1224
> Project: Apache Jena
> Issue Type: Improvement
> Components: TDB
> Affects Versions: Jena 3.1.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
>
> The TDB journal can grow due to write-back being blocked by a long running
> reader, or a succession of overlapping short reads, and many updates.
> This [users@
> email|https://lists.apache.org/thread.html/99b01f1dc7af86e0832279a85da6963985fc9f1f2c36d3c3969aaeb1@%3Cusers.jena.apache.org%3E]
> may be caused by this effect. This accumulated layers of wrappers consume
> heap (<300).
> At some time, lock out new transactions and wait to flush the journal when it
> has many layers in it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
