identify message as a warning
Project: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/commit/621d95d6 Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/621d95d6 Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/621d95d6 Branch: refs/heads/develop Commit: 621d95d6231412661a36472e2d2a1bed3ea55adf Parents: 0b1597a Author: Lisa Owen <[email protected]> Authored: Mon Oct 10 16:56:41 2016 -0700 Committer: Lisa Owen <[email protected]> Committed: Mon Oct 10 16:56:41 2016 -0700 ---------------------------------------------------------------------- clientaccess/g-troubleshooting-connection-problems.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/621d95d6/clientaccess/g-troubleshooting-connection-problems.html.md.erb ---------------------------------------------------------------------- diff --git a/clientaccess/g-troubleshooting-connection-problems.html.md.erb b/clientaccess/g-troubleshooting-connection-problems.html.md.erb index 2cd6815..0328606 100644 --- a/clientaccess/g-troubleshooting-connection-problems.html.md.erb +++ b/clientaccess/g-troubleshooting-connection-problems.html.md.erb @@ -10,4 +10,4 @@ A number of things can prevent a client application from successfully connecting |HAWQ is not running|If the HAWQ master instance is down, users will not be able to connect. You can verify that the HAWQ system is up by running the `hawq state` utility on the HAWQ master host.| |Network problems<br/><br/>Interconnect timeouts|If users connect to the HAWQ master host from a remote client, network problems can prevent a connection \(for example, DNS host name resolution problems, the host system is down, and so on.\). To ensure that network problems are not the cause, connect to the HAWQ master host from the remote client host. For example: `ping hostname`. <br/><br/>If the system cannot resolve the host names and IP addresses of the hosts involved in HAWQ, queries and connections will fail. For some operations, connections to the HAWQ master use `localhost` and others use the actual host name, so you must be able to resolve both. If you encounter this error, first make sure you can connect to each host in your HAWQ array from the master host over the network. In the `/etc/hosts` file of the master and all segments, make sure you have the correct host names and IP addresses for all hosts involved in the HAWQ array. The `127.0.0.1` IP must resolve to `localho st`.| |Too many clients already|By default, HAWQ is configured to allow a maximum of 200 concurrent user connections on the master and 1280 connections on a segment. A connection attempt that causes that limit to be exceeded will be refused. This limit is controlled by the `max_connections` parameter on the master instance and by the `seg_max_connections` parameter on segment instances. If you change this setting for the master, you must also make appropriate changes at the segments.| -|Query failure|Reverse DNS must be configured in your HAWQ cluster network. In cases where reverse DNS has not been configured, failing queries will generate "Failed to reverse DNS lookup for ip \<ip-address\>" messages to the HAWQ master node log file. | +|Query failure|Reverse DNS must be configured in your HAWQ cluster network. In cases where reverse DNS has not been configured, failing queries will generate "Failed to reverse DNS lookup for ip \<ip-address\>" warning messages to the HAWQ master node log file. |
