[jira] [Updated] (OAK-3435) LastRevRecoveryAgent/MissingLastRevSeeker improvements

2015-09-22 Thread Julian Reschke (JIRA)

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

Julian Reschke updated OAK-3435:

Fix Version/s: 1.0.22

> LastRevRecoveryAgent/MissingLastRevSeeker improvements
> --
>
> Key: OAK-3435
> URL: https://issues.apache.org/jira/browse/OAK-3435
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, mongomk, rdbmk
>Affects Versions: 1.0.21, 1.3.6, 1.2.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 1.3.7, 1.2.7, 1.0.22
>
> Attachments: OAK-3435.diff
>
>
> In order to make debugging easier, we should:
> - log exceptions that occur while updating the cluster node info entries
> - when we mark an entry as being recovered, record which cluster node is 
> running the recovery
> - avoid the conditional race condition mentioned in the code comment for 
> acquireRecoveryLock
> - improve logging for cluster node infos that match the current instance id 
> but for some reason will not be recovered



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3435) LastRevRecoveryAgent/MissingLastRevSeeker improvements

2015-09-22 Thread Julian Reschke (JIRA)

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

Julian Reschke updated OAK-3435:

Fix Version/s: 1.2.7

> LastRevRecoveryAgent/MissingLastRevSeeker improvements
> --
>
> Key: OAK-3435
> URL: https://issues.apache.org/jira/browse/OAK-3435
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, mongomk, rdbmk
>Affects Versions: 1.0.21, 1.3.6, 1.2.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 1.3.7, 1.2.7
>
> Attachments: OAK-3435.diff
>
>
> In order to make debugging easier, we should:
> - log exceptions that occur while updating the cluster node info entries
> - when we mark an entry as being recovered, record which cluster node is 
> running the recovery
> - avoid the conditional race condition mentioned in the code comment for 
> acquireRecoveryLock
> - improve logging for cluster node infos that match the current instance id 
> but for some reason will not be recovered



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3435) LastRevRecoveryAgent/MissingLastRevSeeker improvements

2015-09-22 Thread Julian Reschke (JIRA)

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

Julian Reschke updated OAK-3435:

Fix Version/s: 1.3.7

> LastRevRecoveryAgent/MissingLastRevSeeker improvements
> --
>
> Key: OAK-3435
> URL: https://issues.apache.org/jira/browse/OAK-3435
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, mongomk, rdbmk
>Affects Versions: 1.0.21, 1.3.6, 1.2.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 1.3.7
>
> Attachments: OAK-3435.diff
>
>
> In order to make debugging easier, we should:
> - log exceptions that occur while updating the cluster node info entries
> - when we mark an entry as being recovered, record which cluster node is 
> running the recovery
> - avoid the conditional race condition mentioned in the code comment for 
> acquireRecoveryLock
> - improve logging for cluster node infos that match the current instance id 
> but for some reason will not be recovered



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3435) LastRevRecoveryAgent/MissingLastRevSeeker improvements

2015-09-22 Thread Julian Reschke (JIRA)

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

Julian Reschke updated OAK-3435:

Affects Version/s: 1.0.21
   1.3.6
   1.2.6

> LastRevRecoveryAgent/MissingLastRevSeeker improvements
> --
>
> Key: OAK-3435
> URL: https://issues.apache.org/jira/browse/OAK-3435
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, mongomk, rdbmk
>Affects Versions: 1.0.21, 1.3.6, 1.2.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Attachments: OAK-3435.diff
>
>
> In order to make debugging easier, we should:
> - log exceptions that occur while updating the cluster node info entries
> - when we mark an entry as being recovered, record which cluster node is 
> running the recovery
> - avoid the conditional race condition mentioned in the code comment for 
> acquireRecoveryLock
> - improve logging for cluster node infos that match the current instance id 
> but for some reason will not be recovered



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3435) LastRevRecoveryAgent/MissingLastRevSeeker improvements

2015-09-22 Thread Julian Reschke (JIRA)

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

Julian Reschke updated OAK-3435:

Attachment: OAK-3435.diff

Proposed change.

[~egli]] this adds a recoveredBy entry to the cluster node that shows *which* 
node is running the recovery; would that be useful for the discovery service?

> LastRevRecoveryAgent/MissingLastRevSeeker improvements
> --
>
> Key: OAK-3435
> URL: https://issues.apache.org/jira/browse/OAK-3435
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, mongomk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Attachments: OAK-3435.diff
>
>
> In order to make debugging easier, we should:
> - log exceptions that occur while updating the cluster node info entries
> - when we mark an entry as being recovered, record which cluster node is 
> running the recovery
> - avoid the conditional race condition mentioned in the code comment for 
> acquireRecoveryLock
> - improve logging for cluster node infos that match the current instance id 
> but for some reason will not be recovered



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3435) LastRevRecoveryAgent/MissingLastRevSeeker improvements

2015-09-22 Thread Julian Reschke (JIRA)

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

Julian Reschke updated OAK-3435:

Attachment: (was: OAK-3435.diff)

> LastRevRecoveryAgent/MissingLastRevSeeker improvements
> --
>
> Key: OAK-3435
> URL: https://issues.apache.org/jira/browse/OAK-3435
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, mongomk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>
> In order to make debugging easier, we should:
> - log exceptions that occur while updating the cluster node info entries
> - when we mark an entry as being recovered, record which cluster node is 
> running the recovery
> - avoid the conditional race condition mentioned in the code comment for 
> acquireRecoveryLock
> - improve logging for cluster node infos that match the current instance id 
> but for some reason will not be recovered



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3435) LastRevRecoveryAgent/MissingLastRevSeeker improvements

2015-09-22 Thread Julian Reschke (JIRA)

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

Julian Reschke updated OAK-3435:

Attachment: OAK-3435.diff

(proposed change)

> LastRevRecoveryAgent/MissingLastRevSeeker improvements
> --
>
> Key: OAK-3435
> URL: https://issues.apache.org/jira/browse/OAK-3435
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, mongomk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Attachments: OAK-3435.diff
>
>
> In order to make debugging easier, we should:
> - log exceptions that occur while updating the cluster node info entries
> - when we mark an entry as being recovered, record which cluster node is 
> running the recovery
> - avoid the conditional race condition mentioned in the code comment for 
> acquireRecoveryLock
> - improve logging for cluster node infos that match the current instance id 
> but for some reason will not be recovered



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)