Use this page to diagnose connection errors when connecting to a Lindorm instance. Match the error message you received to an entry below, then follow the resolution steps.
Retry exhausted when update config from seedserver
The client cannot reach the Lindorm seed server during connection initialization. The two most common causes are network connectivity and an incorrect port.
Network connectivity
The Elastic Compute Service (ECS) instance and the Lindorm instance cannot reach each other. Make sure that the ECS instance and the Lindorm instance can reach each other. For detailed steps, see Lindorm connection issues and solutions.
Wrong port
The port in your connection string does not match the endpoint type. For the HBase-compatible endpoint, use port 30020.
Failed to connect to jdbc:lindorm:table:url=****
The JDBC driver cannot establish a connection to the LindormTable SQL endpoint. The two most common causes are network connectivity and an incorrect port.
Network connectivity
The ECS instance and the Lindorm instance cannot reach each other. Make sure that the ECS instance and the Lindorm instance can reach each other. For detailed steps, see Lindorm connection issues and solutions.
Wrong port
The port in your JDBC URL does not match the endpoint type. For the LindormTable SQL endpoint, use port 30060. To look up the correct endpoint and port for your instance, see Obtain an endpoint.
DoNotRetryIOException: Detect inefficient query: SELECT*FROM xxxx This query may be a fulltable scan and thus may have unpredictable performance.
The Lindorm wide table engine detected a SELECT statement that would trigger a full table scan. To protect cluster performance, the server rejects the query rather than running it.
Rewrite the query to include a predicate that limits the scan range. For guidance on writing efficient SELECT statements, see the FAQ.