[
https://issues.apache.org/jira/browse/OAK-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-6634.
--------------------------------
Resolution: Fixed
Fixed at http://svn.apache.org/viewvc?rev=1807600&view=rev
The fix reduces the scope of what is protected by the memory barrier to the
compaction phase. This will prevent those bogus log messages.
> Confusing log entries when memory requirements are not met at start of OnRC
> ---------------------------------------------------------------------------
>
> Key: OAK-6634
> URL: https://issues.apache.org/jira/browse/OAK-6634
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Labels: compaction, gc
> Fix For: 1.8, 1.7.7
>
>
> When the memory requirements for running OnRC are not met before the
> estimation phase the estimator will run nevertheless. The process will only
> be cancelled at the beginning of the compaction phase. The entries in the log
> file reflect this:
> {code}
> TarMK GC #1: canceling compaction because available memory level 306.4 MB
> (306395472 bytes) is too low...
> TarMK GC #1: estimation started
> TarMK GC #1: estimation completed in 343.5 ms (343 ms). Estimation skipped
> because of missing gc journal data (expected on first run)
> TarMK GC #1: running full compaction
> TarMK GC #1: compaction started ...
> TarMK GC #1: unable to estimate number of nodes for compaction, missing gc
> history.
> TarMK GC #1: compaction cancelled: Not enough memory.
> TarMK GC #1: cleaning up after failed compaction
> {code}
> However they can easily be (mis-)read as compaction being re-triggered after
> having been cancelled and then being cancelled again.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
