Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DiscoveryIgnoreHostnameFilters do not care instance alias #1400

Open
harunkucuk5 opened this issue Aug 25, 2021 · 0 comments
Open

DiscoveryIgnoreHostnameFilters do not care instance alias #1400

harunkucuk5 opened this issue Aug 25, 2021 · 0 comments

Comments

@harunkucuk5
Copy link

Hi,

We have been using orchestrator with instance aliases, in this way we can have both ip address and hostname information of our instances in orchestrator.

But we have some automated pipelines which create new mysql instances to make recovery and replication restore tests. We do not want to see these test instances on orchestrator . But orchestrator discovers them automatically when they are connected as replica to mysql cluster. after they are destroyed by pipeline orchestrator sees them as dead replicas.

We have realised orchestrator has a filter called DiscoveryIgnoreHostnameFilters which runs hostname based . But since we don't use orchestrator's hostname and mysql hostname resolve methods orchestrator has ip addresses of our instances in hostname field in instance metadata. So the following config is not working because of this. Because this filter does not care instance alias and orchestrator trying to find filter keyword in ip addresses.

"DetectInstanceAliasQuery": "SELECT SUBSTRING_INDEX(@@hostname, '.', 1)",
"DiscoveryIgnoreHostnameFilters": ["auto-verify.*"],

to be able to make this filter work with aliases we need some improvements .

Thanks

@harunkucuk5 harunkucuk5 changed the title DiscoveryIgnoreHostnameFilters does not care instance aliases DiscoveryIgnoreHostnameFilters do not care instance alias Aug 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant