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 "Manfred Baedke (Jira)" <ji...@apache.org> on 2024/11/26 13:38:00 UTC

[jira] (OAK-11284) Greedy Reuse of cluster IDs may lead to synchronous LastRevRecovery executions slowing down startup

    [ https://issues.apache.org/jira/browse/OAK-11284 ]


    Manfred Baedke deleted comment on OAK-11284:
    --------------------------------------

was (Author: baedke):
Turns out that such a system property already exists: [oak.recoveryWaitTimeoutMS|https://github.com/apache/jackrabbit-oak/blob/3fb2678ea3f8d5676872f6bd863761a400795cb9/oak-store-document/src/main/java/org/apache/jackrabbit/oak/plugins/document/RecoveryHandlerImpl.java#L39]

> Greedy Reuse of cluster IDs may lead to synchronous LastRevRecovery executions slowing down startup
> ---------------------------------------------------------------------------------------------------
>
>                 Key: OAK-11284
>                 URL: https://issues.apache.org/jira/browse/OAK-11284
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk
>            Reporter: Manfred Baedke
>            Assignee: Manfred Baedke
>            Priority: Major
>
> Due to OAK-7316, starting Oak instances will take over existing cluster-ids if they do not find one to reuse. If the newly overtaken cluster-id belongs to a mac address / working directory that has not been used for a longer time, the attempt to start a synchronous LastRevRecovery may be costly and even run into a timeout, thus slowing down the startup by the length of this timeout.



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