actions/opensearch-pyd
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Merge pull request #315 from dvillega/bug/spelling-correction

Browse Source 
Minor spelling corrections for documentation
This commit is contained in:
Honza Král
2015-12-10 16:11:34 +01:00
parent a63bad4e1d c39074279a
commit e23fb64b79
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/connection.rst
+1 -1
View File
@@ -3,7 +3,7 @@
Connection Layer API Connection Layer API
==================== ====================
All of the classes reponsible for handling the connection to the Elasticsearch All of the classes responsible for handling the connection to the Elasticsearch
cluster. The default subclasses used can be overriden by passing parameters to the cluster. The default subclasses used can be overriden by passing parameters to the
:class:`~elasticsearch.Elasticsearch` class. All of the arguments to the client :class:`~elasticsearch.Elasticsearch` class. All of the arguments to the client
will be passed on to :class:`~elasticsearch.Transport`, will be passed on to :class:`~elasticsearch.Transport`,
docs/index.rst
+2 -2
View File
@@ -121,7 +121,7 @@ If a connection to a node fails due to connection issues (raises
will be placed on hold for ``dead_timeout`` seconds and the request will be will be placed on hold for ``dead_timeout`` seconds and the request will be
retried on another node. If a connection fails multiple times in a row the retried on another node. If a connection fails multiple times in a row the
timeout will get progressively larger to avoid hitting a node that's, by all timeout will get progressively larger to avoid hitting a node that's, by all
indication, down. If no live connection is availible, the connection that has indication, down. If no live connection is available, the connection that has
the smallest timeout will be used. the smallest timeout will be used.
By default retries are not triggered by a timeout By default retries are not triggered by a timeout
@@ -211,7 +211,7 @@ could come into play.
When using an http load balancer you cannot use the :ref:`sniffing` When using an http load balancer you cannot use the :ref:`sniffing`
functionality - the cluster would supply the client with IP addresses to functionality - the cluster would supply the client with IP addresses to
directly cnnect to the cluster, circumventing the load balancer. Depending on directly connect to the cluster, circumventing the load balancer. Depending on
your configuration this might be something you don't want or break completely. your configuration this might be something you don't want or break completely.
In some environments (notably on Google App Engine) your http requests might be In some environments (notably on Google App Engine) your http requests might be