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

Diagnostics allways returns success:false #2114

Open
zolgera opened this issue Sep 26, 2024 · 1 comment
Open

Diagnostics allways returns success:false #2114

zolgera opened this issue Sep 26, 2024 · 1 comment

Comments

@zolgera
Copy link

zolgera commented Sep 26, 2024

I have maxwell running with connection to the master and the connector is working and reacting on changes in the master (inserts, updates, deletes, ...)

I am running rabbitmq mode

The diagnostics endpoint is always returning success:false

I increased the timeout but same result

{
    "success": false,
    "checks": [
        {
            "name": "binlog-connector",
            "success": false,
            "mandatory": true,
            "resource": "mysql:3306",
            "message": "check did not return after 60000 ms"
        }
    ]
}

Tried to figure out in the sourcecode what diagnostic actually does but did not get far (java not really my thing :))

  • show master status; on the master is working fine with the same user maxwell is using
    settings that I am using
  • --diagnostic=true
  • --http_diagnostic=true
  • --binlog_heartbeat=true

EDIT:
Just saw in the readme
| /diagnostics | for kafka, send a fake message that measures the client to server latency |

So am I right that the diagnostics only works for Kafka instances?

Is there a way to see if the connection to the configured replication_host is still up or it got droped?
Like part of the healthchecks?

@zolgera
Copy link
Author

zolgera commented Sep 26, 2024

Is the Custom health check the only option?

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