[jira] [Updated] (OAK-6886) OffRC always logs 0 for the number of compacted nodes in gc.log

2017-11-20 Thread JIRA 

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

Michael Dürig updated OAK-6886:
---
Fix Version/s: (was: 1.7.14)
   1.7.13

> OffRC always logs 0 for the number of compacted nodes in gc.log
> ---
>
> Key: OAK-6886
> URL: https://issues.apache.org/jira/browse/OAK-6886
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>  Labels: compaction, gc, tooling
> Fix For: 1.8, 1.7.13
>
>
> After an offline compaction the {{gc.log}} always contains 0 for the number 
> of compacted nodes. This is caused by 
> {{org.apache.jackrabbit.oak.segment.tool.Compact.compact()}} instantiating a 
> new {{FileStore}} to run cleanup. That file store has new {{GCMonitor}} 
> instance, which did no see any of the nodes written by the compaction that 
> was run on the previous {{FileStore}} instance. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-6886) OffRC always logs 0 for the number of compacted nodes in gc.log

2017-11-20 Thread JIRA 

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

Michael Dürig updated OAK-6886:
---
Fix Version/s: (was: 1.7.12)
   1.7.14

> OffRC always logs 0 for the number of compacted nodes in gc.log
> ---
>
> Key: OAK-6886
> URL: https://issues.apache.org/jira/browse/OAK-6886
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>  Labels: compaction, gc, tooling
> Fix For: 1.8, 1.7.14
>
>
> After an offline compaction the {{gc.log}} always contains 0 for the number 
> of compacted nodes. This is caused by 
> {{org.apache.jackrabbit.oak.segment.tool.Compact.compact()}} instantiating a 
> new {{FileStore}} to run cleanup. That file store has new {{GCMonitor}} 
> instance, which did no see any of the nodes written by the compaction that 
> was run on the previous {{FileStore}} instance. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-6886) OffRC always logs 0 for the number of compacted nodes in gc.log

2017-11-12 Thread JIRA 

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

Michael Dürig updated OAK-6886:
---
Labels: compaction gc tooling  (was: compaction gc)

> OffRC always logs 0 for the number of compacted nodes in gc.log
> ---
>
> Key: OAK-6886
> URL: https://issues.apache.org/jira/browse/OAK-6886
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>  Labels: compaction, gc, tooling
> Fix For: 1.8, 1.7.12
>
>
> After an offline compaction the {{gc.log}} always contains 0 for the number 
> of compacted nodes. This is caused by 
> {{org.apache.jackrabbit.oak.segment.tool.Compact.compact()}} instantiating a 
> new {{FileStore}} to run cleanup. That file store has new {{GCMonitor}} 
> instance, which did no see any of the nodes written by the compaction that 
> was run on the previous {{FileStore}} instance. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-6886) OffRC always logs 0 for the number of compacted nodes in gc.log

2017-11-06 Thread JIRA 

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

Michael Dürig updated OAK-6886:
---
Fix Version/s: (was: 1.7.11)
   1.7.12

> OffRC always logs 0 for the number of compacted nodes in gc.log
> ---
>
> Key: OAK-6886
> URL: https://issues.apache.org/jira/browse/OAK-6886
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>  Labels: compaction, gc
> Fix For: 1.8, 1.7.12
>
>
> After an offline compaction the {{gc.log}} always contains 0 for the number 
> of compacted nodes. This is caused by 
> {{org.apache.jackrabbit.oak.segment.tool.Compact.compact()}} instantiating a 
> new {{FileStore}} to run cleanup. That file store has new {{GCMonitor}} 
> instance, which did no see any of the nodes written by the compaction that 
> was run on the previous {{FileStore}} instance. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-6886) OffRC always logs 0 for the number of compacted nodes in gc.log

2017-10-31 Thread JIRA 

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

Michael Dürig updated OAK-6886:
---
Summary: OffRC always logs 0 for the number of compacted nodes in gc.log  
(was: OffRC alway logs 0 for the number of compacted nodes in gc.log)

> OffRC always logs 0 for the number of compacted nodes in gc.log
> ---
>
> Key: OAK-6886
> URL: https://issues.apache.org/jira/browse/OAK-6886
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>  Labels: compaction, gc
> Fix For: 1.8, 1.7.12
>
>
> After an offline compaction the {{gc.log}} always contains 0 for the number 
> of compacted nodes. This is caused by 
> {{org.apache.jackrabbit.oak.segment.tool.Compact.compact()}} instantiating a 
> new {{FileStore}} to run cleanup. That file store has new {{GCMonitor}} 
> instance, which did no see any of the nodes written by the compaction that 
> was run on the previous {{FileStore}} instance. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)