You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
Tried to figure out in the sourcecode what diagnostic actually does but did not get far (java not really my thing :))
settings that I am using
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?
The text was updated successfully, but these errors were encountered: