Skip to content

The dynamic name of InstanceName doesn't work when using SwitchOnRebuild #34

@perosb

Description

@perosb

The CM spec uses a dynamic name for "InstanceName".

When using SwitchOnRebuild, CM stores active/rebuild collection in Properties table with the InstanceName as part of the KEY.
Since the name is different for k8s deployments/restarts, the key changes hence it cannot find any references and uses the default index instead of the currently active collection.

Support ticket CS0215027

This is the same issue we found in 9.0 when using PaaS deployments and slots. In that case it was partially solved using a "index-catalogue" (which has other issues tho).

Since the default k8s spec setup only uses a single CM instance it might work with "InstanceName: cm"? (We use multiple CMs and need to named them explicitly)

The same is true for the docker-compose that leaves this empty which uses the container hostname. This of course only applies if running with SwitchOnRebuild.

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