search

datastax / zdm-proxy-automation

An Ansible-based automation suite to deploy and manage the Zero Downtime Migration Proxy
https://docs.datastax.com/en/astra-serverless/docs/migrate/introduction.html
Apache License 2.0
60 stars 5 forks source link

Missing node in cluster leads to timeout for proxy client #51

Closed carlduevel closed 1 year ago

carlduevel commented 1 year ago

Switching an application to use the proxy instead of talking to C* directly timeouts occur on and off on the application side:

[com.datastax.oss.driver.api.core.DriverTimeoutException: [s0|control|id: 0x795f84e4, L:/172.18.0.3:48592 - R:cassandra_proxy/172.18.0.2:9042] Protocol initialization request, step 1 (OPTIONS): timed out after 5000 ms]

Matching lines in the proxy log:

Client Handler could not be created: ORIGIN-CONNECTOR context timed out or cancelled while opening connection to ORIGIN: context deadline exceeded

Though the error message does not contain an IP address I presume this is caused by a faulty entry in the C* table that pointed to a non-existing node, because the IP of that node is coming up in the proxy log before the error.

My question is: As the application with the DataStax Java Driver did not have a problem connecting to the cluster with the missing node why is the proxy?

┆Issue is synchronized with this Jira Task by Unito ┆Components: Automation ┆Priority: Major ┆Resolution: Done

sync-by-unito[bot] commented 1 year ago

➤ Wei Deng commented:

duplicate