This topic describes the errors that may occur when you connect to a Lindorm instance and how to troubleshoot the errors.

The following table describes the error messages that may appear and how to troubleshoot the errors.

Error message Possible cause and solution
Retry exhausted when update config from seedserver
  • If you want to connect to a Lindorm instance from an Elastic Compute Service (ECS) instance, make sure that the ECS instance and the Lindorm instance can reach each other. For more information, see Lindorm connection issues and solutions.
  • This error may be returned because the port number that you specified to connect to the Lindorm instance is invalid. For example, if you want to use the HBase-compatible endpoint to connect to the Lindorm instance, specify 30020 as the port number.
Failed to connect to jdbc:lindorm:table:url=****
  • If you want to connect to a Lindorm instance from an ECS instance, make sure that the ECS instance and the Lindorm instance can reach each other. For more information, see Lindorm connection issues and solutions.
  • The error may be returned because the port number that you specified to connect to the Lindorm instance is invalid. For example, if you want to use the LindormTable SQL endpoint to connect to the Lindorm instance, specify 30060 as the port number. For information about how to obtain the port number, see Obtain an endpoint.
DoNotRetryIOException: Detect inefficient query: SELECT*FROM xxxx This query may be a fulltable scan and thus may have unpredictable performance. This error is returned because the Lindorm wide table engine identifies the SELECT statement as an inefficient query and the server rejects to execute the statement. For information about how to resolve the error, see FAQ.