[jira] [Updated] (OAK-7285) Reindexing using --doc-traversal-mode can OOM while aggregation in some cases
[
https://issues.apache.org/jira/browse/OAK-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-7285:
---
Labels: (was: candidate_oak_1_8)
> Reindexing using --doc-traversal-mode can OOM while aggregation in some cases
> -
>
> Key: OAK-7285
> URL: https://issues.apache.org/jira/browse/OAK-7285
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene, mongomk
>Affects Versions: 1.8.0
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Major
> Fix For: 1.9.0, 1.10, 1.8.3
>
>
> {{--doc-traversal-mode}} works on the notion of {{preferred}} children which
> is computed using path fragments that form aggregate rules.
> The idea is reading through aggregated paths should avoid keeping non useful
> nodes (for path being currently indexed) in memory.
> But, currently, in case, say when there multiple preferred children -
> {{jcr:content}}, {{metadata}}, then an index defn indexing parent of a very
> deep tree root would try to read in the whole tree before concluding that it
> doesn't have preferred children
> e.g. with preferred list - {{jcr:content}} and {{metadata}} and index looking
> for {{jcr:content}} indexing following structure
> {noformat}
> + /path/being/indexed
>+ very
> + very
> + very
>+ deep
>+ tree
> + /some-sibling
> {noformat}
> Currently, while looking for {{jcr:content}}, the code concludes that it
> doesn't exist only after reaching {{/some-sibling}} (or if number of children
> read of {{/path/being/indexed}} is >= num_preferred_children).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7285) Reindexing using --doc-traversal-mode can OOM while aggregation in some cases
[
https://issues.apache.org/jira/browse/OAK-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-7285:
---
Fix Version/s: 1.8.3
> Reindexing using --doc-traversal-mode can OOM while aggregation in some cases
> -
>
> Key: OAK-7285
> URL: https://issues.apache.org/jira/browse/OAK-7285
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene, mongomk
>Affects Versions: 1.8.0
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Major
> Fix For: 1.9.0, 1.10, 1.8.3
>
>
> {{--doc-traversal-mode}} works on the notion of {{preferred}} children which
> is computed using path fragments that form aggregate rules.
> The idea is reading through aggregated paths should avoid keeping non useful
> nodes (for path being currently indexed) in memory.
> But, currently, in case, say when there multiple preferred children -
> {{jcr:content}}, {{metadata}}, then an index defn indexing parent of a very
> deep tree root would try to read in the whole tree before concluding that it
> doesn't have preferred children
> e.g. with preferred list - {{jcr:content}} and {{metadata}} and index looking
> for {{jcr:content}} indexing following structure
> {noformat}
> + /path/being/indexed
>+ very
> + very
> + very
>+ deep
>+ tree
> + /some-sibling
> {noformat}
> Currently, while looking for {{jcr:content}}, the code concludes that it
> doesn't exist only after reaching {{/some-sibling}} (or if number of children
> read of {{/path/being/indexed}} is >= num_preferred_children).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7285) Reindexing using --doc-traversal-mode can OOM while aggregation in some cases
[
https://issues.apache.org/jira/browse/OAK-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-7285:
Description:
{{--doc-traversal-mode}} works on the notion of {{preferred}} children which is
computed using path fragments that form aggregate rules.
The idea is reading through aggregated paths should avoid keeping non useful
nodes (for path being currently indexed) in memory.
But, currently, in case, say when there multiple preferred children -
{{jcr:content}}, {{metadata}}, then an index defn indexing parent of a very
deep tree root would try to read in the whole tree before concluding that it
doesn't have preferred children
e.g. with preferred list - {{jcr:content}} and {{metadata}} and index looking
for {{jcr:content}} indexing following structure
{noformat}
+ /path/being/indexed
+ very
+ very
+ very
+ deep
+ tree
+ /some-sibling
{noformat}
Currently, while looking for {{jcr:content}}, the code concludes that it
doesn't exist only after reaching {{/some-sibling}} (or if number of children
read of {{/path/being/indexed}} is >= num_preferred_children).
was:
{{--doc-traversal-mode}} works on the notion of {{preferred}} children which is
computed using path fragments that form aggregate rules.
The idea is reading through aggregated paths should avoid keeping non useful
nodes (for path being currently indexed) in memory.
But, currently, in case, say when there multiple preferred children -
{{jcr:content}}, {{metadata}}, then an index defn indexing parent of a very
deep tree root would try to read in the whole tree before concluding that it
doesn't have preferred children
e.g. with preferred list - {{j:c}} and {{md} and index looking for {{j:c}}
indexing following structure
{noformat}
+ /path/being/indexed
+ very
+ very
+ very
+ deep
+ tree
+ /some-sibling
{noformat}
Currently, while looking for {{j:c}}, the code concludes that it doesn't exist
only after reaching {{/some-sibling}} (or if number of children read of
{{/path/being/indexed}} is >= num_preferred_children).
> Reindexing using --doc-traversal-mode can OOM while aggregation in some cases
> -
>
> Key: OAK-7285
> URL: https://issues.apache.org/jira/browse/OAK-7285
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene, mongomk
>Affects Versions: 1.8.0
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Major
> Labels: candidate_oak_1_8
> Fix For: 1.10
>
>
> {{--doc-traversal-mode}} works on the notion of {{preferred}} children which
> is computed using path fragments that form aggregate rules.
> The idea is reading through aggregated paths should avoid keeping non useful
> nodes (for path being currently indexed) in memory.
> But, currently, in case, say when there multiple preferred children -
> {{jcr:content}}, {{metadata}}, then an index defn indexing parent of a very
> deep tree root would try to read in the whole tree before concluding that it
> doesn't have preferred children
> e.g. with preferred list - {{jcr:content}} and {{metadata}} and index looking
> for {{jcr:content}} indexing following structure
> {noformat}
> + /path/being/indexed
>+ very
> + very
> + very
>+ deep
>+ tree
> + /some-sibling
> {noformat}
> Currently, while looking for {{jcr:content}}, the code concludes that it
> doesn't exist only after reaching {{/some-sibling}} (or if number of children
> read of {{/path/being/indexed}} is >= num_preferred_children).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
