[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Dulceanu updated OAK-5661: - Fix Version/s: (was: 1.38.0) 1.40.0 > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.40.0 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Dulceanu updated OAK-5661: - Fix Version/s: (was: 1.36.0) > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.38.0 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Dulceanu updated OAK-5661: - Fix Version/s: 1.38.0 > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.36.0, 1.38.0 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5661: -- Fix Version/s: (was: 1.14.0) > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.16.0 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5661: -- Fix Version/s: 1.16.0 > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.14.0, 1.16.0 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5661: -- Fix Version/s: (was: 1.12.0) > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.14.0 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5661: -- Fix Version/s: 1.14.0 > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.12.0, 1.14.0 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5661: -- Fix Version/s: (was: 1.10.0) > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.12 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5661: -- Fix Version/s: 1.12 > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.10.0, 1.12 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-5661: Sprint: L16 > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.10 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-5661: Sprint: (was: L16) > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.10 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5661) Make NRT indexing resilient against unbounded growth
[ https://issues.apache.org/jira/browse/OAK-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-5661: - Fix Version/s: (was: 1.8) 1.10 > Make NRT indexing resilient against unbounded growth > > > Key: OAK-5661 > URL: https://issues.apache.org/jira/browse/OAK-5661 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.10 > > > NRT Indexes for volatile indexes [1] can grow large if async index update > faces issues. Like if it gets stuck for days or due to some bug index do not > get updates like in OAK-5649 then the sizes can grow very large. > For such cases we should add some checks in logic where system can ensure > that some cleanup is performed or writes to indexes are stopped. Also such a > situation should be flagged > [1] Indexes which see lots of addition and deletions. So effective indexing > size is smaller however if deletions are not applied (as is the case with > NRT) such indexes can grow large -- This message was sent by Atlassian JIRA (v6.4.14#64029)
