[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-3054: - Attachment: OAK-3054-v3.patch v3 attached. moved the _updates_ variable a bit. > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Assignee: Alex Parvulescu > Labels: resilience, tooling > Fix For: 1.3.9, 1.0.23, 1.2.8 > > Attachments: OAK-3054-v1.patch, OAK-3054-v2.patch, OAK-3054-v3.patch > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-3054: - Attachment: OAK-3054-v2.patch attached update patch. one improvement is calling _indexStats.setUpdates(this.updates);_ on the AsyncUpdateCallback#close method so that the number of updates will reflect the real number, instead of the number%100 that is being logged via #indexUpdate method. > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Assignee: Alex Parvulescu > Labels: resilience, tooling > Fix For: 1.3.9, 1.0.23, 1.2.8 > > Attachments: OAK-3054-v1.patch, OAK-3054-v2.patch > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-3054: - Priority: Major (was: Minor) > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Assignee: Alex Parvulescu > Labels: resilience, tooling > Fix For: 1.3.9, 1.0.23, 1.2.8 > > Attachments: OAK-3054-v1.patch > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-3054: - Fix Version/s: 1.0.23 > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Assignee: Alex Parvulescu >Priority: Minor > Labels: resilience, tooling > Fix For: 1.3.9, 1.0.23, 1.2.8 > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-3054: - Attachment: OAK-3054-v1.patch proposed patch. [~chetanm] please review? > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Assignee: Alex Parvulescu >Priority: Minor > Labels: resilience, tooling > Fix For: 1.3.9, 1.0.23, 1.2.8 > > Attachments: OAK-3054-v1.patch > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3054: -- Fix Version/s: (was: 1.3.8) 1.3.9 > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Priority: Minor > Labels: resilience, tooling > Fix For: 1.3.9, 1.2.8 > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3054: -- Fix Version/s: (was: 1.2.7) 1.2.8 > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Priority: Minor > Labels: resilience, tooling > Fix For: 1.3.8, 1.2.8 > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain updated OAK-3054: --- Fix Version/s: (was: 1.3.7) 1.3.8 > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Priority: Minor > Labels: resilience, tooling > Fix For: 1.3.8, 1.2.7 > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-3054: -- Fix Version/s: (was: 1.3.6) 1.3.7 > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Priority: Minor > Labels: resilience, tooling > Fix For: 1.3.7, 1.2.6 > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain updated OAK-3054: --- Fix Version/s: (was: 1.2.5) 1.2.6 > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Priority: Minor > Labels: resilience, tooling > Fix For: 1.3.6, 1.2.6 > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain updated OAK-3054: --- Fix Version/s: (was: 1.3.5) 1.3.6 > IndexStatsMBean should provide some details if the async indexing is failing > > > Key: OAK-3054 > URL: https://issues.apache.org/jira/browse/OAK-3054 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Chetan Mehrotra >Priority: Minor > Labels: resilience, tooling > Fix For: 1.3.6, 1.2.5 > > > If the background indexing fails for some reason it logs the exception for > the first time then it logs the exception like _The index update failed ..._. > After that if indexing continues to fail then no further logging is done so > as to avoid creating noise. > This poses a problem on long running system where original exception might > not be noticed and index does not show updated result. For such cases we > should expose the indexing health as part of {{IndexStatsMBean}}. Also we can > provide the last recorded exception. > Administrator can then check for MBean and enable debug logs for further > troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain updated OAK-3054: --- Fix Version/s: (was: 1.2.4) 1.2.5 IndexStatsMBean should provide some details if the async indexing is failing Key: OAK-3054 URL: https://issues.apache.org/jira/browse/OAK-3054 Project: Jackrabbit Oak Issue Type: Improvement Components: query Reporter: Chetan Mehrotra Priority: Minor Labels: resilience, tooling Fix For: 1.3.5, 1.2.5 If the background indexing fails for some reason it logs the exception for the first time then it logs the exception like _The index update failed ..._. After that if indexing continues to fail then no further logging is done so as to avoid creating noise. This poses a problem on long running system where original exception might not be noticed and index does not show updated result. For such cases we should expose the indexing health as part of {{IndexStatsMBean}}. Also we can provide the last recorded exception. Administrator can then check for MBean and enable debug logs for further troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-3054: --- Labels: resilience tooling (was: ) IndexStatsMBean should provide some details if the async indexing is failing Key: OAK-3054 URL: https://issues.apache.org/jira/browse/OAK-3054 Project: Jackrabbit Oak Issue Type: Improvement Components: query Reporter: Chetan Mehrotra Priority: Minor Labels: resilience, tooling Fix For: 1.2.4, 1.3.5 If the background indexing fails for some reason it logs the exception for the first time then it logs the exception like _The index update failed ..._. After that if indexing continues to fail then no further logging is done so as to avoid creating noise. This poses a problem on long running system where original exception might not be noticed and index does not show updated result. For such cases we should expose the indexing health as part of {{IndexStatsMBean}}. Also we can provide the last recorded exception. Administrator can then check for MBean and enable debug logs for further troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3054: -- Fix Version/s: (was: 1.3.4) 1.3.5 IndexStatsMBean should provide some details if the async indexing is failing Key: OAK-3054 URL: https://issues.apache.org/jira/browse/OAK-3054 Project: Jackrabbit Oak Issue Type: Improvement Components: query Reporter: Chetan Mehrotra Priority: Minor Fix For: 1.2.4, 1.3.5 If the background indexing fails for some reason it logs the exception for the first time then it logs the exception like _The index update failed ..._. After that if indexing continues to fail then no further logging is done so as to avoid creating noise. This poses a problem on long running system where original exception might not be noticed and index does not show updated result. For such cases we should expose the indexing health as part of {{IndexStatsMBean}}. Also we can provide the last recorded exception. Administrator can then check for MBean and enable debug logs for further troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-3054: - Fix Version/s: (was: 1.0.18) IndexStatsMBean should provide some details if the async indexing is failing Key: OAK-3054 URL: https://issues.apache.org/jira/browse/OAK-3054 Project: Jackrabbit Oak Issue Type: Improvement Components: query Reporter: Chetan Mehrotra Priority: Minor Fix For: 1.2.4, 1.3.4 If the background indexing fails for some reason it logs the exception for the first time then it logs the exception like _The index update failed ..._. After that if indexing continues to fail then no further logging is done so as to avoid creating noise. This poses a problem on long running system where original exception might not be noticed and index does not show updated result. For such cases we should expose the indexing health as part of {{IndexStatsMBean}}. Also we can provide the last recorded exception. Administrator can then check for MBean and enable debug logs for further troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3054: -- Fix Version/s: (was: 1.3.3) 1.3.4 Bulk move to 1.3.4 IndexStatsMBean should provide some details if the async indexing is failing Key: OAK-3054 URL: https://issues.apache.org/jira/browse/OAK-3054 Project: Jackrabbit Oak Issue Type: Improvement Components: query Reporter: Chetan Mehrotra Priority: Minor Fix For: 1.2.4, 1.3.4, 1.0.18 If the background indexing fails for some reason it logs the exception for the first time then it logs the exception like _The index update failed ..._. After that if indexing continues to fail then no further logging is done so as to avoid creating noise. This poses a problem on long running system where original exception might not be noticed and index does not show updated result. For such cases we should expose the indexing health as part of {{IndexStatsMBean}}. Also we can provide the last recorded exception. Administrator can then check for MBean and enable debug logs for further troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-3054: - Fix Version/s: (was: 1.0.17) (was: 1.2.3) 1.0.18 1.2.4 IndexStatsMBean should provide some details if the async indexing is failing Key: OAK-3054 URL: https://issues.apache.org/jira/browse/OAK-3054 Project: Jackrabbit Oak Issue Type: Improvement Components: query Reporter: Chetan Mehrotra Priority: Minor Fix For: 1.2.4, 1.3.3, 1.0.18 If the background indexing fails for some reason it logs the exception for the first time then it logs the exception like _The index update failed ..._. After that if indexing continues to fail then no further logging is done so as to avoid creating noise. This poses a problem on long running system where original exception might not be noticed and index does not show updated result. For such cases we should expose the indexing health as part of {{IndexStatsMBean}}. Also we can provide the last recorded exception. Administrator can then check for MBean and enable debug logs for further troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
[ https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3054: -- Fix Version/s: (was: 1.3.2) 1.3.3 Bulk move to 1.3.3. IndexStatsMBean should provide some details if the async indexing is failing Key: OAK-3054 URL: https://issues.apache.org/jira/browse/OAK-3054 Project: Jackrabbit Oak Issue Type: Improvement Components: query Reporter: Chetan Mehrotra Priority: Minor Fix For: 1.2.3, 1.3.3, 1.0.17 If the background indexing fails for some reason it logs the exception for the first time then it logs the exception like _The index update failed ..._. After that if indexing continues to fail then no further logging is done so as to avoid creating noise. This poses a problem on long running system where original exception might not be noticed and index does not show updated result. For such cases we should expose the indexing health as part of {{IndexStatsMBean}}. Also we can provide the last recorded exception. Administrator can then check for MBean and enable debug logs for further troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)