Continuent Community

I have a simple two node cluster where replication is working from a master to a slave. The cctrl command shows both hosts in the cluster, but when I try to use the Tungsten connector it hangs when I try to connect using a mysql client with a valid username/password. If i specify an incorrect user/password it will return immediately with an authentication error. What may be causing the hangup?

When I turn on the connector trace this is as far as it gets.

jvm 1 | DEBUG [MySQLConnectionHandler] - Start serving client: /10.10.212.74:54221
jvm 1 | DEBUG [ProtocolHandler] - Connection string: jdbc:t-router://default/test
jvm 1 | DEBUG [ProtocolHandler] - User: tungsten Password: secret
jvm 1 | DEBUG [RouterURL] - Parsed t-router URL: service=default dbname=test QOS=RW_STRICT maxAppliedLatency=<undef> props={user=tungsten, password=secret}
jvm 1 | DEBUG [DataService] - Connecting to driver: url=jdbc:t-router://default/test{user=tungsten, password=secret} info={user=tungsten, password=secret}


>>> Gilles Rayrat
You're most likely facing a situation where your router doesn't find any online data server to send the requests to, so it pause the request, waiting for one to become available.
What is the output of the "ls" command under the manager CLI (tungsten-manager/bin/cctrl)?

I had recently been experiencing a problem with an OutOfMemoryError so perhaps it offlined my datasources. In an attempt to reset my environment I stopped the Tungsten processes and cleared the contents of history and trep_commit_seqno. After restarting the processes it allowed me to login to the connector.

In the event that this happens to me again, is there a way that I can configure a timeout on the connector to respond with a message about "no datasources online"? Otherwise my clients seem to wait indefinitely for a response.

Hi Jon,
You'll want to look at the router.properties file that can be found in the cluster-home/conf directory
Depending on your needs, you'll need to modified the following flags:
waitForDisconnect=true
waitForDisconnectTimeout=60
waitIfUnavailable=true
waitIfUnavailableTimeout=0
waitIfDisabled=true
waitIfDisabledTimeout=0

The config file should have sufficient comments for you to make your decision. Don't hesitate to report back if you need further help or if this made the trick

Cheers,
Gilles.