Skip to content

Cluster-view consistency & safeguards #28

Description

@radim

Today the DryRun is opportunistic and assumes the latest activity stats come from all nodes at the same time. The point-in-time cluster view needs to be more consistent.

  • Per-node freshness vs stale-node policy
  • gap detection

And somehow it needs to deal with changing shape of the whole PostgreSQL cluster deployment.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions