[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-2126: Fix Version/s: (was: 1.3.7) > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Labels: resilience > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-2126: Fix Version/s: (was: 1.3.6) 1.3.7 > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Labels: resilience > Fix For: 1.3.7 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-2126: --- Fix Version/s: (was: 1.3.5) 1.3.6 > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Labels: resilience > Fix For: 1.3.6 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-2126: -- Fix Version/s: (was: 1.3.4) 1.3.5 > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Labels: resilience > Fix For: 1.3.5 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-2126: -- Fix Version/s: (was: 1.3.3) 1.3.4 Bulk move to 1.3.4 > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Labels: resilience > Fix For: 1.3.4 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-2126: -- Fix Version/s: (was: 1.3.2) 1.3.3 Bulk move to 1.3.3. > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Labels: resilience > Fix For: 1.3.3 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-2126: -- Fix Version/s: (was: 1.3.1) 1.3.2 Bulk move to 1.3.2 > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Labels: resilience > Fix For: 1.3.2 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-2126: -- Fix Version/s: (was: 1.3.0) 1.3.1 Bulk move to 1.3.1 > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Labels: resilience > Fix For: 1.3.1 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-2126: --- Labels: resilience (was: ) > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Labels: resilience > Fix For: 1.3.0 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-2126: --- Fix Version/s: (was: 1.2) 1.3.0 > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Fix For: 1.3.0 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-2126: -- Fix Version/s: (was: 1.1.1) 1.2 > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Fix For: 1.2 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2126) retry strategy for failed JDBC requests
[ https://issues.apache.org/jira/browse/OAK-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain updated OAK-2126: --- Fix Version/s: (was: 1.1) 1.1.1 > retry strategy for failed JDBC requests > --- > > Key: OAK-2126 > URL: https://issues.apache.org/jira/browse/OAK-2126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: rdbmk >Reporter: Julian Reschke > Fix For: 1.1.1 > > > Discussion: should we have a retry strategy for failed commits? > Things to consider: > - does this potentially interfere with other retry strategies (either on a > lower layer or in the DocumentMK)? > - what failure scenarios would it address? > - how to test those? > - how to configure it? > - what would be good defaults? (number of retries, interval) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
