Yang

"orchestrator user with SUPER privilege" and "The MySQL server is running with the --super-read-only" is two things ? check the MySQL server whether set super-read-only.

try again. `forget-cluster` is not locked.

if configed like this:`"PromotionIgnoreHostnameFilters": [""]`, the `config.Config.PromotionIgnoreHostnameFilters` will be empty, that is `[]`. So this is not a problem. ------------split line ---------------- ignore above. I think I misunderstand it. `[""]`...

There is a problem with replication in debian-dbserv2. ``` 2021-07-21 14:20:47 DEBUG - sorted replica: debian-dbserv1:3306 mysql-bin.000002:156 2021-07-21 14:20:47 DEBUG - sorted replica: debian-dbserv2:3306 :0 ``` `debian-dbserv2` can not change...

Sorry，I didn't write clearly. I mean, try these steps: 1.config `DiscoveryIgnoreMasterHostnameFilters` as above 2.restart `orchestrator` 3.forget the cluster 4. just discover the instance `10.40.0.9`

maybe here: https://github.com/openark/orchestrator/tags

after old master set read only, whether super account still write?

The graceful-takeover set old master read only first, and this will trigger `RecoverNonWriteableMaster`. try this: disable auto failover before graceful-takeover.