[jira] [Assigned] (OAK-9851) Provide support for throttling in mongo oak client based on oplog replication window

["Marcel Reutegger (Jira)" <ji...@apache.org>]

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

Marcel Reutegger reassigned OAK-9851:
-------------------------------------

    Assignee: Marcel Reutegger

> Provide support for throttling in mongo oak client based on oplog replication window
> ------------------------------------------------------------------------------------
>
>                 Key: OAK-9851
>                 URL: https://issues.apache.org/jira/browse/OAK-9851
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>            Reporter: Rishabh Kumar
>            Assignee: Marcel Reutegger
>            Priority: Major
>
> In prod envs, Mongo works in Primary/Secondary configuration where writes happens on primary and secondaries replicate them asynchronously from primary's oplog.rs collection.
>  
> In case there is huge skipe in mongo (may be under huge load or some inernal sharding) the oplog window can drop to few minutes, thus creating a risk for secondaries to fall-off oplog window and going into initial-sync phase.
>  
> This can be catastrophic if during this initial-sync phase the primary goes down and hence mongo will become unavailable and we might need to setup new cluster from snapshots.
>  
> To avoid this, I propose to add throttling into mongo oak client in case oplog window drops below a certain threshold.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)