Skip to content

single replsets restart pod failed #2087

@jisongxi

Description

@jisongxi

Report

when I config replsets size to 1, and restart the pod when modify the cpu or mem, the mongo pod will start , but it will start failed!, because the mongo primry record the old pod ip, the new mongo po start the ip is changed, so the mongo will not register it in, the primary is the old pod ip

More about the problem

rs.status()
{
"ok" : 0,
"errmsg" : "Our replica set config is invalid or we are not a member of it",
"code" : 93,
"codeName" : "InvalidReplicaSetConfig"
}

Steps to reproduce

Versions

  1. Kubernetes
  2. Operator
  3. Database

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions