[ 
https://issues.apache.org/jira/browse/OAK-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Egli updated OAK-5602:
-----------------------------
    Description: As a follow up of OAK-5601: that one is about a situation 
where backgroundRead falls way behind and journal GC cleans up journal entries 
before it was able to read it. We should generally look into improving this 
situation, eg by having journal GC not do the clean up as long as there are 
instances that haven't read the entry. This could perhaps be achieved by 
periodically having each instance inform the rest about what journal entries it 
has processed (or simpler: how far back it would be -find- fine for journal 
entries to be GC'ed)  (was: As a follow up of OAK-5601: that one is about a 
situation where backgroundRead falls way behind and journal GC cleans up 
journal entries before it was able to read it. We should generally look into 
improving this situation, eg by having journal GC not do the clean up as long 
as there are instances that haven't read the entry. This could perhaps be 
achieved by periodically having each instance inform the rest about what 
journal entries it has processed (or simpler: how far back it would be find for 
journal entries to be GC'ed))

> avoid missing journal entries
> -----------------------------
>
>                 Key: OAK-5602
>                 URL: https://issues.apache.org/jira/browse/OAK-5602
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.6.0
>            Reporter: Stefan Egli
>             Fix For: 1.7.0, 1.8
>
>
> As a follow up of OAK-5601: that one is about a situation where 
> backgroundRead falls way behind and journal GC cleans up journal entries 
> before it was able to read it. We should generally look into improving this 
> situation, eg by having journal GC not do the clean up as long as there are 
> instances that haven't read the entry. This could perhaps be achieved by 
> periodically having each instance inform the rest about what journal entries 
> it has processed (or simpler: how far back it would be -find- fine for 
> journal entries to be GC'ed)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to