Use the PG_TERMINATE_BACKEND command to shut down any idle sessions.If you have a large number of open connections, consider the following approaches: Use the STV_SESSIONS table to view information about the active user sessions for Amazon Redshift: select * from stv_sessions Use the STL_CONNECTION_LOG table to check your open connections: select recordtime, username, dbname, remotehost, remoteportĤ. Look for the DatabaseConnections metric in your Amazon CloudWatch Logs entries.ģ. To verify the number of open connections in your Amazon Redshift cluster, perform the following steps:Ģ. For ds2.8xlarge, dc2.8xlarge, ra3.xlplus, ra3.4xlarge and ra3.16xlarge nodes, the max connection limit is 2,000. When there are too many open connections in your Amazon Redshift cluster, you receive the following error: Error: FATAL: connection limit / exceeded for userĪs the error message indicates, 500 is the max connection limit for dc2.large and ds2.xlarge node types in Amazon Redshift. If the SSL connection is a requirement for your use case or environment, make sure that your connection string includes the required SSL parameter.įor example: jdbc:redshift://.:5439/dev?ssl=true Fatal connection error.The parameter group can be edited from the Parameters tab of the Amazon Redshift console. You can change the SSL configuration by editing the parameter group that's associated with your Amazon Redshift cluster. Update the require_ssl parameter back to false, which is default parameter value.If your SSL configuration is set to true, then consider the following approaches: (Optional) Verify your SSL configuration using the AWS Command Line Interface (AWS CLI): describe-cluster-parameters Modify the parameter group that's associated with your Amazon Redshift cluster.Ĥ. To confirm whether the require_ssl parameter is set to true, perform the following steps:ģ. If your Amazon Redshift cluster requires SSL to be enabled for any connection, then you might receive the following connection error: Error: (500310) Invalid operation: no pg_hba.conf entry for host "::ffff:", user "username", database "dbname", SSL off Your firewall might be blocking the Amazon Redshift port (the default port is 5439). If the telnet command indicates that your Amazon Redshift cluster connection is successful but your cluster remains inaccessible, then check your network's firewall. The CIDR range or IP you are connecting to the Amazon Redshift cluster from is added in the Security Group’s ingress rule.The Amazon Redshift port (default 5439) of type TCP is allowed in the Security Group’s inbound rule.If the telnet command indicates that your Amazon Redshift cluster connection is unsuccessful, then verify that the following conditions are true: To test the connection to your Amazon Redshift cluster, use the telnet command: telnet Telnet is unsuccessful or Amazon Redshift cluster remains inaccessible To confirm that your client can reach the private IP address of the Amazon Redshift cluster's leader node, use the dig command: dig Be sure that your cluster isn't set to Publicly Accessible.The NAT Gateway allows clusters in a private subnet to connect to the internet. Be sure to attach the NAT Gateway to the public subnet’s route table.If your Amazon Redshift cluster resides in a private subnet, then check the following: To test connectivity, use telnet to test the connection to your Amazon Redshift cluster: telnet The Amazon Redshift cluster resides in a private subnet Confirm that you have an internet gateway attached to your route table.Confirm that the Amazon Redshift cluster is set to "Publicly Accessible." For more information about publicly accessible options, see Managing clusters in a VPC.If you're trying to connect to an Amazon Redshift cluster that resides in a public subnet, then check the following: The Amazon Redshift cluster resides in a public subnet The network configurations must be the same for both the old and new subnets. If your Amazon Redshift cluster wasn't resized or restored recently, then verify your network configurations. The cluster must be launched in the same subnet from before the snapshot resize or restore. If your Amazon Redshift cluster was recently resized or restored from a snapshot, then check your cluster's subnet. Resolution The Amazon Redshift cluster was recently resized or restored from a snapshot
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |