Re: Cluster discovery results not stored in backend?

281 views
Skip to first unread message

Shlomi Noach

unread,
Jun 7, 2018, 5:48:00 AM6/7/18
to nomor...@gmail.com, orchestrator-mysql
Hi, please answer these:
What is your topology? How many servers? Which is the master? What were you expecting to see in `-c topology`?

what is the output of:

orchestrator-client -c all-instances

what is the output of:

prchestrator-client -c clusters

You are using `DiscoverByShowSlaveHosts: true`. Do you have `report_host` and `report_port` configured on all servers? What are the values for this params on all servers?

On Thu, Jun 7, 2018 at 1:14 AM, <nomor...@gmail.com> wrote:
Hi all,

I've got orchestrator running successfully, and (after a few tweaks to the configs) I'm able to discovery instances.  However, it seems that the backend database isn't being updated, because when I use the cluster view (either through the UI or via the orchestrator-client), it says "Unable to determine cluster name".  Here are the steps I'm using:

1) Clone github repo.
2) docker build -t orchestrator:latest . (after modifying to include my config file)
3) docker run -P orchestrator:latest

> 2018-06-06 21:32:32 DEBUG Connected to orchestrator backend: orchestrator:?@tcp(example.com:3306)/orchestrator?timeout=2s
> 2018-06-06 21:32:32 DEBUG Orchestrator pool SetMaxOpenConns: 128
> 2018-06-06 21:32:32 DEBUG Initializing orchestrator
> 2018-06-06 21:32:32 DEBUG Migrating database schema
> 2018-06-06 21:32:50 DEBUG Migrated database schema to version [3.0.11]
> 2018-06-06 21:32:50 INFO Connecting to backend example.com:3306: maxConnections: 128, maxIdleConns: 32
> 2018-06-06 21:32:50 INFO Starting Discovery
> 2018-06-06 21:32:50 INFO Registering endpoints
> 2018-06-06 21:32:50 INFO continuous discovery: setting up
> 2018-06-06 21:32:50 INFO Starting HTTP listener on :3000
> 2018-06-06 21:32:51 INFO continuous discovery: starting
> 2018-06-06 21:32:51 DEBUG Queue.startMonitoring(DEFAULT)

4) ./resources/bin/orchestrator-client -c discover -i myhost:3306

> myhost:3306

5) ./resources/bin/orchestrator-client -c topology -i myhost:3306

> 2018-06-06 22:09:36 ERROR Unable to determine cluster name

I don't see any errors in the logs.  I've included my config file below.  Any idea what I could be doing wrong?

Thanks!

------

{
  "#": "-----",
  "#": "this is a comment. See further comment hints below.",
  "#": "-----",
  "Debug": true,
  "ListenAddress": ":3000",
  "MySQLTopologyUser": "orchestrator",
  "MySQLTopologyPassword": "*******",
  "MySQLOrchestratorHost": "example.com",
  "MySQLOrchestratorPort": 3306,
  "MySQLOrchestratorDatabase": "orchestrator",
  "MySQLOrchestratorUser": "orchestrator",
  "MySQLOrchestratorPassword": "*******",
  "#": "-----",
  "#": "The above is all you need for initial setup. Below is more advanced stuff",
  "#": "-----",
  "DiscoverByShowSlaveHosts": true,
  "InstancePollSeconds": 5,
  "HostnameResolveMethod": "default",
  "MySQLHostnameResolveMethod": "@@report_host",
  "ReasonableReplicationLagSeconds": 10,
  "ProblemIgnoreHostnameFilters": [],
  "AuditLogFile": "",
  "AuditToSyslog": false,
  "SlaveLagQuery": "",
  "DetectClusterAliasQuery": "SELECT SUBSTRING_INDEX(@@report_host, '.', -2)",
  "DetectClusterDomainQuery": "",
  "DetectDataCenterQuery": "SELECT @@report_host",
  "PhysicalEnvironmentPattern": "",
  "PromotionIgnoreHostnameFilters": [],
  "#": "-----",
  "#": "security, access control:",
  "#": "-----",
  "ReadOnly": false,
  "AuthenticationMethod": "",
  "HTTPAuthUser": "",
  "HTTPAuthPassword": "",
  "AuthUserHeader": "",
  "PowerAuthUsers": [
    "*"
  ],
  "#": "-----",
  "#": "Pseudo-GTID config:",
  "#": "-----",
  "PseudoGTIDPattern": "",
  "PseudoGTIDPatternIsFixedSubstring": false,
  "PseudoGTIDMonotonicHint": "asc:",
  "DetectPseudoGTIDQuery": "",
  "#": "-----",
  "#": "Recovery related config:",
  "#": "-----",
  "FailureDetectionPeriodBlockMinutes": 60,
  "RecoveryPeriodBlockSeconds": 3600,
  "RecoveryIgnoreHostnameFilters": [],
  "RecoverMasterClusterFilters": [
    "_master_pattern_"
  ],
  "RecoverIntermediateMasterClusterFilters": [
    "_intermediate_master_pattern_"
  ],
  "OnFailureDetectionProcesses": [
    "echo 'Detected {failureType} on {failureCluster}. Affected replicas: {countSlaves}' >> /tmp/recovery.log"
  ],
  "PreGracefulTakeoverProcesses": [
    "echo 'Planned takeover about to take place on {failureCluster}. Master will switch to read_only' >> /tmp/recovery.log"
  ],
  "PreFailoverProcesses": [
    "echo 'Will recover from {failureType} on {failureCluster}' >> /tmp/recovery.log"
  ],
  "PostFailoverProcesses": [
    "echo '(for all types) Recovered from {failureType} on {failureCluster}. Failed: {failedHost}:{failedPort}; Successor: {successorHost}:{successorPort}' >> /tmp/recovery.log"
  ],
  "PostUnsuccessfulFailoverProcesses": [],
  "PostMasterFailoverProcesses": [
    "echo 'Recovered from {failureType} on {failureCluster}. Failed: {failedHost}:{failedPort}; Promoted: {successorHost}:{successorPort}' >> /tmp/recovery.log"
  ],
  "PostIntermediateMasterFailoverProcesses": [
    "echo 'Recovered from {failureType} on {failureCluster}. Failed: {failedHost}:{failedPort}; Successor: {successorHost}:{successorPort}' >> /tmp/recovery.log"
  ],
  "PostGracefulTakeoverProcesses": [
    "echo 'Planned takeover complete' >> /tmp/recovery.log"
  ],
  "DetachLostSlavesAfterMasterFailover": true,
  "ApplyMySQLPromotionAfterMasterFailover": false,
  "MasterFailoverDetachSlaveMasterHost": false,
  "MasterFailoverLostInstancesDowntimeMinutes": 60,
  "PostponeSlaveRecoveryOnLagMinutes": 10,
  "#": "-----",
  "GraphiteAddr": "",
  "GraphitePath": "",
  "GraphiteConvertHostnameDotsToUnderscores": true
}

--
You received this message because you are subscribed to the Google Groups "orchestrator-mysql" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orchestrator-mysql+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orchestrator-mysql/9cb79b41-dfef-48a4-8666-f8cb127746db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

nomor...@gmail.com

unread,
Jun 7, 2018, 10:51:28 AM6/7/18
to orchestrator-mysql
Sorry, I deleted my post soon after, because I finally figured it out.  The problem was that my default storage backend was set to BLACKHOLE, so obviously the Orchestrator data wasn't getting persisted.  Little wonder!  In my topology, I have some of my replication servers just for filtering and proxying data, which is why those servers use the BLACKHOLE storage engine.

lli...@gmail.com

unread,
Feb 14, 2020, 10:01:41 PM2/14/20
to orchestrator-mysql

Hi,

 I am having the same error in Orchestrator log. I am using Orchestrator with SQLlite and raft algorithm running in Kubernetes.
 This is what I get from error log when 
  "2020-02-15 02:44:17 ERROR Unable to determine cluster name. clusterHint=mysqd8-0b-002:4301
  [martini] Completed 500 Internal Server Error in 15.974331ms"

 If I use clusterName instead of cluster hint or if I use host/port/destHost/destPort graceful takeover works fine. Otherwise it fails with error: 
 {"Code":"ERROR","Message":"2020-02-15 02:44:17 ERROR Unable to determine cluster name. clusterHint=mysqd8-0b-002:4301","Details":null}

Sorry for re-opening this post but I did not see an y otehr posts with similar error.
 Thank you,
 Liviu


Shlomi Noach

unread,
Feb 15, 2020, 2:56:21 PM2/15/20
to lli...@gmail.com, orchestrator-mysql
Hi,

> This is what I get from error log when 

Can you please explain what you were doing? I only see what the logs says, but what was the command you were running?

What is your config?
What is your topology? Can you run orchestrator-clcient -c topology -alias the-alias ?


To unsubscribe from this group and stop receiving emails from it, send an email to orchestrator-my...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "orchestrator-mysql" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orchestrator-my...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orchestrator-mysql/b3a14827-90bb-461f-8b7a-ace00e19a7cc%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages