You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/03/09 05:23:38 UTC

[jira] [Commented] (OAK-1500) Verify restore to revision on MongoNS

    [ https://issues.apache.org/jira/browse/OAK-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352532#comment-14352532 ] 

Chetan Mehrotra commented on OAK-1500:
--------------------------------------

[~amitj_76] Assigning this issue to you. Can you close it if your test were successful and no more work is to be done for this issue

> Verify restore to revision on MongoNS
> -------------------------------------
>
>                 Key: OAK-1500
>                 URL: https://issues.apache.org/jira/browse/OAK-1500
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Alex Parvulescu
>            Assignee: Chetan Mehrotra
>            Priority: Critical
>              Labels: production
>             Fix For: 1.2
>
>
> Following the discussion on OAK-1339, the backup will be controlled from Mongo directly, but we still need to verify 2 things:
>  - ongoing transactions will be discarded on restore, the head has to point to the latest stable revision
>  - as an added benefit, the restore could happen to an older revision (see the sharded setup where a node can get ahead of the others between the moment the backup starts and when it will finish across the board)



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