Abstract: Embodiments are directed towards managing designations of a plurality of files across multiple clusters. Files may be designated as primary files or secondary files. Primary files at one cluster may be asynchronously replicated at another cluster as secondary files. Secondary files may be synchronously validated with remote primary files based on local file access requests. If a write request for a local secondary file is provided, then the local file may be designated as the primary file and the remote file may be designated as the secondary file. Local access may then be provided to the local primary file. If a read request for a local secondary file is provide, then local access may be provided to the local secondary file without changing file designations. In some embodiments, file designations may be preemptively changed based on a file change designation schedule for clusters at different geographic locations.

Abstract: Embodiments are directed towards managing an impact of a plurality of system and/or maintenance tasks distributed across a plurality of nodes. At least one initiator node may provide at least one disk request to at least one disk on at least one participant node. Each disk on each participant node with a workload, such as request wait time, above a maximum threshold and/or below a minimum threshold may be determined. If a disk is determined to have a workload above a maximum threshold and/or below a minimum threshold, then an impact of respective tasks on initiator nodes that provided requests to the determined disks may be reduced and/or increased, respectively. In some embodiments, an initiator node may reduce or increase an impact of a task by reducing or increasing a number of threads executing on that initiator node for that task.