You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/11/10 15:12:11 UTC

[jira] [Commented] (OAK-3613) Backport TarMK revision gc related issues

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

Michael Dürig commented on OAK-3613:
------------------------------------

Tentative lists of issues and revisions to back port (order by revision)

OAK-2734: Compaction does not finish on repository with continuous writes ([1675311|http://svn.apache.org/r1675311])
OAK-2862: CompactionMap#compress() inefficient for large compaction maps ([1678958|http://svn.apache.org/r1678958], [1679959|http://svn.apache.org/r1679959], [1679995|http://svn.apache.org/r1679995], [1683780|http://svn.apache.org/r1683780])
OAK-3051: Improve compaction gain estimation logging for the case where there are no tar readers ([1691589|http://svn.apache.org/r1691589])
OAK-3139: SNFE in persisted comapation map when using CLEAN_OLD  ([1693022|http://svn.apache.org/r1693022], [1693195|http://svn.apache.org/r1693195])
OAK-3179: Deadlock between persisted compaction map and cleanup  ([1694208|http://svn.apache.org/r1694208])
OAK-3177: Compaction slow on repository with continuous writes  ([1694497|http://svn.apache.org/r1694497])
OAK-3264: Deadlock between persisted compaction map and cleanup 2 ( [1696956|http://svn.apache.org/r1696956])
OAK-2875: Namespaces keep references to old node states ([1697423|http://svn.apache.org/r1697423])
OAK-3317: ConcurrentModificationException when running SegmentOverflowExceptionIT ([1700252|http://svn.apache.org/r1700252])
OAK-3347: Ineffective cleanup after compaction due to references to root ([1701239|http://svn.apache.org/r1701239])
OAK-3329: TarMK cleanup blocks writers ([1706818|http://svn.apache.org/r1706818])
OAK-3481: CompationMapTest does not close file store ([1706974|http://svn.apache.org/r1706974])
OAK-3172: Unreleased closed sessions can keep a root reference from getting collected ([1707073|http://svn.apache.org/r1707073])
OAK-3290: Revision gc blocks repository shutdown ([1707681|http://svn.apache.org/r1707681])
OAK-3502: Improve logging during cleanup ([1707753|http://svn.apache.org/r1707753])
OAK-3501: PersistedCompactionMap could release reference to records early ([1708051|http://svn.apache.org/r1708051])
OAK-3511: Test failure: CompactionMapTest.removeSome ([1708297|http://svn.apache.org/r1708297], [1708298|http://svn.apache.org/r1708298])
OAK-3330: FileStore lock contention with concurrent writers ([1708401|http://svn.apache.org/r1708401], [1708402|http://svn.apache.org/r1708402], [1708403|http://svn.apache.org/r1708403])
OAK-3506: Uniformization of compaction log messages ([1708447|http://svn.apache.org/r1708447], [1710629|http://svn.apache.org/r1710629])


> Backport TarMK revision gc related issues
> -----------------------------------------
>
>                 Key: OAK-3613
>                 URL: https://issues.apache.org/jira/browse/OAK-3613
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: segmentmk
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: compaction, gc
>             Fix For: 1.2.8, 1.0.24
>
>
> Some of the issues related to TarMK revision gc should be back ported to the branches. This issue is for keeping track of which issues and which svn revisions we consider for back porting. The task consists of the following steps:
> # Identify issue to back port
> # Merge the respective commits into a private forks of the 1.0 and 1.2 branches
> # Run tests on builds from the private forks
> # On success merge the private forks to the 1.0 and 1.2 branches and update the fix versions of the respective issues. This probably requires manually updating the svn merge info with the respective svn revisions. 
> [~dhasler]: FYI
> [~alex.parvulescu], [~frm]: please refrain from merging potential conflicting changes into the branches in the meanwhile. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)