Skip to content

Investigate behaviour of force-merge during shard relocation #93503

New issue
New issue
Closed
Closed
Investigate behaviour of force-merge during shard relocation#93503
Labels
:Distributed Coordination/AllocationAll issues relating to the decision making around placing a shard (both master logic & on the nodes)Team:Distributed (Obsolete)Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
@DaveCTurner

Description

@DaveCTurner
DaveCTurner
opened on Feb 6, 2023

If a shard is undergoing a long-running force merge and we decide to relocate it onto a different node, I believe (but have not checked) that we do not take any action to cancel the force-merge. Is that right? Do we do the right thing in terms of tracking the disk usage of the shard while the force merge is still running?

Metadata

Metadata

Assignees

No one assigned

    Labels

    :Distributed Coordination/AllocationAll issues relating to the decision making around placing a shard (both master logic & on the nodes)Team:Distributed (Obsolete)Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy