From 21ea552070d7e512c9c0b8cd521f67bff4d1249e Mon Sep 17 00:00:00 2001 From: Dongjoon Hyun Date: Tue, 9 Feb 2016 02:07:32 -0800 Subject: [PATCH] Fix typos in docs. --- docs/java-api/query-dsl/geo-queries.asciidoc | 2 +- docs/java-api/query-dsl/geo-shape-query.asciidoc | 2 +- docs/plugins/integrations.asciidoc | 2 +- docs/reference/aggregations/bucket/range-aggregation.asciidoc | 2 +- .../aggregations/bucket/reverse-nested-aggregation.asciidoc | 2 +- .../analysis/tokenfilters/compound-word-tokenfilter.asciidoc | 2 +- docs/reference/index-modules/allocation/filtering.asciidoc | 2 +- docs/reference/indices/flush.asciidoc | 2 +- docs/reference/indices/shard-stores.asciidoc | 2 +- docs/reference/ingest/ingest.asciidoc | 4 ++-- docs/reference/mapping/fields/routing-field.asciidoc | 2 +- docs/reference/mapping/fields/ttl-field.asciidoc | 2 +- docs/reference/mapping/params/index.asciidoc | 2 +- docs/reference/mapping/params/properties.asciidoc | 2 +- docs/reference/mapping/params/similarity.asciidoc | 2 +- docs/reference/mapping/types.asciidoc | 2 +- docs/reference/mapping/types/geo-point.asciidoc | 2 +- docs/reference/migration/migrate_1_0.asciidoc | 4 ++-- docs/reference/migration/migrate_2_0/index_apis.asciidoc | 2 +- docs/reference/migration/migrate_2_0/mapping.asciidoc | 2 +- docs/reference/migration/migrate_3_0.asciidoc | 2 +- docs/reference/modules/cluster.asciidoc | 2 +- docs/reference/modules/cluster/allocation_filtering.asciidoc | 4 ++-- docs/reference/modules/network.asciidoc | 2 +- docs/reference/query-dsl/geo-queries.asciidoc | 2 +- docs/reference/query-dsl/template-query.asciidoc | 4 ++-- docs/reference/search/profile.asciidoc | 4 ++-- docs/reference/search/request/inner-hits.asciidoc | 4 ++-- docs/reference/search/search-template.asciidoc | 4 ++-- docs/reference/search/suggesters/term-suggest.asciidoc | 4 ++-- docs/reference/setup/as-a-service.asciidoc | 2 +- docs/reference/setup/configuration.asciidoc | 2 +- 32 files changed, 40 insertions(+), 40 deletions(-) diff --git a/docs/java-api/query-dsl/geo-queries.asciidoc b/docs/java-api/query-dsl/geo-queries.asciidoc index ea68ce1aaba..18ed0f37c14 100644 --- a/docs/java-api/query-dsl/geo-queries.asciidoc +++ b/docs/java-api/query-dsl/geo-queries.asciidoc @@ -10,7 +10,7 @@ The queries in this group are: <> query:: Find document with geo-shapes which either intersect, are contained by, or - do not interesect with the specified geo-shape. + do not intersect with the specified geo-shape. <> query:: diff --git a/docs/java-api/query-dsl/geo-shape-query.asciidoc b/docs/java-api/query-dsl/geo-shape-query.asciidoc index a9b952ddf28..c753cd72c1a 100644 --- a/docs/java-api/query-dsl/geo-shape-query.asciidoc +++ b/docs/java-api/query-dsl/geo-shape-query.asciidoc @@ -32,7 +32,7 @@ to your classpath in order to use this type: [source,java] -------------------------------------------------- -// Import ShapeRelationn and ShapeBuilder +// Import ShapeRelation and ShapeBuilder import org.elasticsearch.common.geo.ShapeRelation; import org.elasticsearch.common.geo.builders.ShapeBuilder; -------------------------------------------------- diff --git a/docs/plugins/integrations.asciidoc b/docs/plugins/integrations.asciidoc index fd44629dd29..a24ad00f226 100644 --- a/docs/plugins/integrations.asciidoc +++ b/docs/plugins/integrations.asciidoc @@ -43,7 +43,7 @@ releases 2.0 and later do not support rivers. * https://www.elastic.co/guide/en/logstash/current/plugins-inputs-elasticsearch.html[Elasticsearch input to Logstash] The Logstash `elasticsearch` input plugin. * https://www.elastic.co/guide/en/logstash/current/plugins-filters-elasticsearch.html[Elasticsearch event filtering in Logstash] - The Logstash `elasticearch` filter plugin. + The Logstash `elasticsearch` filter plugin. * https://www.elastic.co/guide/en/logstash/current/plugins-codecs-es_bulk.html[Elasticsearch bulk codec] The Logstash `es_bulk` plugin decodes the Elasticsearch bulk format into individual events. diff --git a/docs/reference/aggregations/bucket/range-aggregation.asciidoc b/docs/reference/aggregations/bucket/range-aggregation.asciidoc index d428d44523f..44760fc728f 100644 --- a/docs/reference/aggregations/bucket/range-aggregation.asciidoc +++ b/docs/reference/aggregations/bucket/range-aggregation.asciidoc @@ -2,7 +2,7 @@ === Range Aggregation A multi-bucket value source based aggregation that enables the user to define a set of ranges - each representing a bucket. During the aggregation process, the values extracted from each document will be checked against each bucket range and "bucket" the relevant/matching document. -Note that this aggregration includes the `from` value and excludes the `to` value for each range. +Note that this aggregation includes the `from` value and excludes the `to` value for each range. Example: diff --git a/docs/reference/aggregations/bucket/reverse-nested-aggregation.asciidoc b/docs/reference/aggregations/bucket/reverse-nested-aggregation.asciidoc index a25fc83733b..03bcdb0a18c 100644 --- a/docs/reference/aggregations/bucket/reverse-nested-aggregation.asciidoc +++ b/docs/reference/aggregations/bucket/reverse-nested-aggregation.asciidoc @@ -77,7 +77,7 @@ tags of the issues the user has commented on: } -------------------------------------------------- -As you can see above, the the `reverse_nested` aggregation is put in to a `nested` aggregation as this is the only place +As you can see above, the `reverse_nested` aggregation is put in to a `nested` aggregation as this is the only place in the dsl where the `reversed_nested` aggregation can be used. Its sole purpose is to join back to a parent doc higher up in the nested structure. diff --git a/docs/reference/analysis/tokenfilters/compound-word-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/compound-word-tokenfilter.asciidoc index 1644d177218..f77c47d156e 100644 --- a/docs/reference/analysis/tokenfilters/compound-word-tokenfilter.asciidoc +++ b/docs/reference/analysis/tokenfilters/compound-word-tokenfilter.asciidoc @@ -34,7 +34,7 @@ Credits for the hyphenation code go to the Apache FOP project . [float] === Dictionary decompounder -The `dictionary_decompounder` uses a brute force approach in conjuction with +The `dictionary_decompounder` uses a brute force approach in conjunction with only the word dictionary to find subwords in a compound word. It is much slower than the hyphenation decompounder but can be used as a first start to check the quality of your dictionary. diff --git a/docs/reference/index-modules/allocation/filtering.asciidoc b/docs/reference/index-modules/allocation/filtering.asciidoc index 4c2b7f41a87..784fa1af24c 100644 --- a/docs/reference/index-modules/allocation/filtering.asciidoc +++ b/docs/reference/index-modules/allocation/filtering.asciidoc @@ -16,7 +16,7 @@ attribute as follows: ------------------------ bin/elasticsearch --node.rack rack1 --node.size big <1> ------------------------ -<1> These attribute settings can also be specfied in the `elasticsearch.yml` config file. +<1> These attribute settings can also be specified in the `elasticsearch.yml` config file. These metadata attributes can be used with the `index.routing.allocation.*` settings to allocate an index to a particular diff --git a/docs/reference/indices/flush.asciidoc b/docs/reference/indices/flush.asciidoc index ef8cd27548b..b02fb15135b 100644 --- a/docs/reference/indices/flush.asciidoc +++ b/docs/reference/indices/flush.asciidoc @@ -186,7 +186,7 @@ Here is what it looks like when one shard group failed due to pending operations } -------------------------------------------------- -NOTE: The above error is shown when the synced flush failes due to concurrent indexing operations. The HTTP +NOTE: The above error is shown when the synced flush fails due to concurrent indexing operations. The HTTP status code in that case will be `409 CONFLICT`. Sometimes the failures are specific to a shard copy. The copies that failed will not be eligible for diff --git a/docs/reference/indices/shard-stores.asciidoc b/docs/reference/indices/shard-stores.asciidoc index 2b3712b2241..f2718c3e705 100644 --- a/docs/reference/indices/shard-stores.asciidoc +++ b/docs/reference/indices/shard-stores.asciidoc @@ -3,7 +3,7 @@ Provides store information for shard copies of indices. Store information reports on which nodes shard copies exist, the shard -copy allocation ID, a unique identifer for each shard copy, and any exceptions +copy allocation ID, a unique identifier for each shard copy, and any exceptions encountered while opening the shard index or from earlier engine failure. By default, only lists store information for shards that have at least one diff --git a/docs/reference/ingest/ingest.asciidoc b/docs/reference/ingest/ingest.asciidoc index 7df3bebb006..17a6d2d6e12 100644 --- a/docs/reference/ingest/ingest.asciidoc +++ b/docs/reference/ingest/ingest.asciidoc @@ -61,7 +61,7 @@ All processors are defined in the following way within a pipeline definition: Each processor defines its own configuration parameters, but all processors have the ability to declare `tag` and `on_failure` fields. These fields are optional. -A `tag` is simply a string identifier of the specific instatiation of a certain +A `tag` is simply a string identifier of the specific instantiation of a certain processor in a pipeline. The `tag` field does not affect any processor's behavior, but is very useful for bookkeeping and tracing errors to specific processors. @@ -1079,7 +1079,7 @@ response: It is often useful to see how each processor affects the ingest document as it is passed through the pipeline. To see the intermediate results of -each processor in the simulat request, a `verbose` parameter may be added +each processor in the simulate request, a `verbose` parameter may be added to the request Here is an example verbose request and its response: diff --git a/docs/reference/mapping/fields/routing-field.asciidoc b/docs/reference/mapping/fields/routing-field.asciidoc index f71bbbf0cc0..deb46178ccf 100644 --- a/docs/reference/mapping/fields/routing-field.asciidoc +++ b/docs/reference/mapping/fields/routing-field.asciidoc @@ -24,7 +24,7 @@ GET my_index/my_type/1?routing=user1 <2> // AUTOSENSE <1> This document uses `user1` as its routing value, instead of its ID. -<2> The the same `routing` value needs to be provided when +<2> The same `routing` value needs to be provided when <>, <>, or <> the document. diff --git a/docs/reference/mapping/fields/ttl-field.asciidoc b/docs/reference/mapping/fields/ttl-field.asciidoc index 9bfdc72b4c4..1fd258d1ea1 100644 --- a/docs/reference/mapping/fields/ttl-field.asciidoc +++ b/docs/reference/mapping/fields/ttl-field.asciidoc @@ -93,7 +93,7 @@ used for future documents. ==== Note on documents expiration -Expired documents will be automatically deleted periodoically. The following +Expired documents will be automatically deleted periodically. The following settings control the expiry process: `indices.ttl.interval`:: diff --git a/docs/reference/mapping/params/index.asciidoc b/docs/reference/mapping/params/index.asciidoc index 979ead036f0..6dd9151814d 100644 --- a/docs/reference/mapping/params/index.asciidoc +++ b/docs/reference/mapping/params/index.asciidoc @@ -22,7 +22,7 @@ are searchable. It accepts three values: This option applies only to `string` fields, for which it is the default. The string field value is first <> to convert the string into terms (e.g. a list of individual words), which are then - indexed. At search time, the the query string is passed through + indexed. At search time, the query string is passed through (<>) the same analyzer to generate terms in the same format as those in the index. It is this process that enables <>. diff --git a/docs/reference/mapping/params/properties.asciidoc b/docs/reference/mapping/params/properties.asciidoc index c0d1670d2db..7683272ea19 100644 --- a/docs/reference/mapping/params/properties.asciidoc +++ b/docs/reference/mapping/params/properties.asciidoc @@ -7,7 +7,7 @@ contain sub-fields, called `properties`. These properties may be of any be added: * explicitly by defining them when <>. -* explicitily by defining them when adding or updating a mapping type with the <> API. +* explicitly by defining them when adding or updating a mapping type with the <> API. * <> just by indexing documents containing new fields. Below is an example of adding `properties` to a mapping type, an `object` diff --git a/docs/reference/mapping/params/similarity.asciidoc b/docs/reference/mapping/params/similarity.asciidoc index 5f2245ad2f3..0cdbd80a93e 100644 --- a/docs/reference/mapping/params/similarity.asciidoc +++ b/docs/reference/mapping/params/similarity.asciidoc @@ -22,7 +22,7 @@ configuration are: `BM25`:: The Okapi BM25 algorithm. - See {defguide}/pluggable-similarites.html[Plugggable Similarity Algorithms] + See {defguide}/pluggable-similarites.html[Pluggable Similarity Algorithms] for more information. diff --git a/docs/reference/mapping/types.asciidoc b/docs/reference/mapping/types.asciidoc index 60d96577a43..2ac579f273a 100644 --- a/docs/reference/mapping/types.asciidoc +++ b/docs/reference/mapping/types.asciidoc @@ -21,7 +21,7 @@ document: <>:: `nested` for arrays of JSON objects [float] -=== Geo dataypes +=== Geo datatypes <>:: `geo_point` for lat/lon points <>:: `geo_shape` for complex shapes like polygons diff --git a/docs/reference/mapping/types/geo-point.asciidoc b/docs/reference/mapping/types/geo-point.asciidoc index ad7230e68d6..e724a5428b2 100644 --- a/docs/reference/mapping/types/geo-point.asciidoc +++ b/docs/reference/mapping/types/geo-point.asciidoc @@ -9,7 +9,7 @@ Fields of type `geo_point` accept latitude-longitude pairs, which can be used: <> cell. * to aggregate documents by <> or by <> from a central point. -* to integerate distance into a document's <>. +* to integrate distance into a document's <>. * to <> documents by distance. There are four ways that a geo-point may be specified, as demonstrated below: diff --git a/docs/reference/migration/migrate_1_0.asciidoc b/docs/reference/migration/migrate_1_0.asciidoc index f8cfad2f71c..d7428fa34cc 100644 --- a/docs/reference/migration/migrate_1_0.asciidoc +++ b/docs/reference/migration/migrate_1_0.asciidoc @@ -44,7 +44,7 @@ The <>, <>, <> and <> APIs have all been changed to make their format more RESTful and less clumsy. -For instance, if you just want the `nodes` section of the the `cluster_state`, +For instance, if you just want the `nodes` section of the `cluster_state`, instead of: [source,sh] @@ -320,7 +320,7 @@ longer be used to return whole objects and it no longer accepts the parameters instead. * Settings, like `index.analysis.analyzer.default` are now returned as proper - nested JSON objects, which makes them easier to work with programatically: + nested JSON objects, which makes them easier to work with programmatically: + [source,js] --------------- diff --git a/docs/reference/migration/migrate_2_0/index_apis.asciidoc b/docs/reference/migration/migrate_2_0/index_apis.asciidoc index d305f7a9d8c..c177a887866 100644 --- a/docs/reference/migration/migrate_2_0/index_apis.asciidoc +++ b/docs/reference/migration/migrate_2_0/index_apis.asciidoc @@ -25,7 +25,7 @@ Index templates can no longer be configured on disk. Use the ==== Analyze API changes -The Analyze API now returns the the `position` of the first token as `0` +The Analyze API now returns the `position` of the first token as `0` instead of `1`. The `prefer_local` parameter has been removed. The `_analyze` API is a light diff --git a/docs/reference/migration/migrate_2_0/mapping.asciidoc b/docs/reference/migration/migrate_2_0/mapping.asciidoc index 09170a2e718..24c56f4b254 100644 --- a/docs/reference/migration/migrate_2_0/mapping.asciidoc +++ b/docs/reference/migration/migrate_2_0/mapping.asciidoc @@ -153,7 +153,7 @@ PUT my_index } } ---------------------------- -<1> These two fields cannot be distinguised as both are referred to as `foo.bar`. +<1> These two fields cannot be distinguished as both are referred to as `foo.bar`. You can no longer create fields with dots in the name. diff --git a/docs/reference/migration/migrate_3_0.asciidoc b/docs/reference/migration/migrate_3_0.asciidoc index 9e95f9dd865..705b23d1ea0 100644 --- a/docs/reference/migration/migrate_3_0.asciidoc +++ b/docs/reference/migration/migrate_3_0.asciidoc @@ -550,7 +550,7 @@ Removing individual setters for lon() and lat() values, both values should be se Removing setters for to(Object ...) and from(Object ...) in favour of the only two allowed input arguments (String, Number). Removing setter for center point (point(), geohash()) because parameter is mandatory and should already be set in constructor. -Also removing setters for lt(), lte(), gt(), gte() since they can all be replaced by equivallent +Also removing setters for lt(), lte(), gt(), gte() since they can all be replaced by equivalent calls to to/from() and inludeLower()/includeUpper(). ==== GeoPolygonQueryBuilder diff --git a/docs/reference/modules/cluster.asciidoc b/docs/reference/modules/cluster.asciidoc index 37a2927b67d..5d7bac10917 100644 --- a/docs/reference/modules/cluster.asciidoc +++ b/docs/reference/modules/cluster.asciidoc @@ -17,7 +17,7 @@ There are a number of settings available to control the shard allocation process be distributed across different racks or availability zones. * <> allows certain nodes or groups of nodes excluded - from allocation so that they can be decommisioned. + from allocation so that they can be decommissioned. Besides these, there are a few other <>. diff --git a/docs/reference/modules/cluster/allocation_filtering.asciidoc b/docs/reference/modules/cluster/allocation_filtering.asciidoc index d465de04b76..051c88ac9cd 100644 --- a/docs/reference/modules/cluster/allocation_filtering.asciidoc +++ b/docs/reference/modules/cluster/allocation_filtering.asciidoc @@ -7,10 +7,10 @@ you to allow or disallow the allocation of shards from *any* index to particular nodes. The typical use case for cluster-wide shard allocation filtering is when you -want to decommision a node, and you would like to move the shards from that +want to decommission a node, and you would like to move the shards from that node to other nodes in the cluster before shutting it down. -For instance, we could decomission a node using its IP address as follows: +For instance, we could decommission a node using its IP address as follows: [source,js] -------------------------------------------------- diff --git a/docs/reference/modules/network.asciidoc b/docs/reference/modules/network.asciidoc index 5a710598206..f71dc83ac5b 100644 --- a/docs/reference/modules/network.asciidoc +++ b/docs/reference/modules/network.asciidoc @@ -28,7 +28,7 @@ Defaults to `_local_`. `discovery.zen.ping.unicast.hosts`:: In order to join a cluster, a node needs to know the hostname or IP address of -at least some of the other nodes in the cluster. This settting provides the +at least some of the other nodes in the cluster. This setting provides the initial list of other nodes that this node will try to contact. Accepts IP addresses or hostnames. + diff --git a/docs/reference/query-dsl/geo-queries.asciidoc b/docs/reference/query-dsl/geo-queries.asciidoc index ca7064fda72..9aaf286526d 100644 --- a/docs/reference/query-dsl/geo-queries.asciidoc +++ b/docs/reference/query-dsl/geo-queries.asciidoc @@ -11,7 +11,7 @@ The queries in this group are: <> query:: Find document with geo-shapes which either intersect, are contained by, or - do not interesect with the specified geo-shape. + do not intersect with the specified geo-shape. <> query:: diff --git a/docs/reference/query-dsl/template-query.asciidoc b/docs/reference/query-dsl/template-query.asciidoc index 14a439bb3ee..104adffe630 100644 --- a/docs/reference/query-dsl/template-query.asciidoc +++ b/docs/reference/query-dsl/template-query.asciidoc @@ -77,7 +77,7 @@ GET /_search } } ------------------------------------------ -<1> Name of the the query template in `config/scripts/`, i.e., `my_template.mustache`. +<1> Name of the query template in `config/scripts/`, i.e., `my_template.mustache`. Alternatively, you can register a query template in the special `.scripts` index with: @@ -106,7 +106,7 @@ GET /_search } } ------------------------------------------ -<1> Name of the the query template in `config/scripts/`, i.e., `storedTemplate.mustache`. +<1> Name of the query template in `config/scripts/`, i.e., `storedTemplate.mustache`. There is also a dedicated `template` endpoint, allows you to template an entire search request. diff --git a/docs/reference/search/profile.asciidoc b/docs/reference/search/profile.asciidoc index 6e11b4c7650..530e41f2678 100644 --- a/docs/reference/search/profile.asciidoc +++ b/docs/reference/search/profile.asciidoc @@ -261,7 +261,7 @@ The meaning of the stats are as follows: This parameter shows how long it takes to build a Scorer for the query. A Scorer is the mechanism that iterates over matching documents generates a score per-document (e.g. how well does "foo" match the document?). - Note, this records the time required to generate the Scorer object, not actuall score the documents. Some + Note, this records the time required to generate the Scorer object, not actual score the documents. Some queries have faster or slower initialization of the Scorer, depending on optimizations, complexity, etc. {empty} + {empty} + @@ -353,7 +353,7 @@ For reference, the various collector reason's are: `search_min_score`:: A collector that only returns matching documents that have a score greater than `n`. This is seen when - the top-level paramenter `min_score` has been specified. + the top-level parameter `min_score` has been specified. `search_multi`:: diff --git a/docs/reference/search/request/inner-hits.asciidoc b/docs/reference/search/request/inner-hits.asciidoc index 09d995bbd27..4b47c883ce0 100644 --- a/docs/reference/search/request/inner-hits.asciidoc +++ b/docs/reference/search/request/inner-hits.asciidoc @@ -148,14 +148,14 @@ nested level these can also be returned via the `fields` feature. An important default is that the `_source` returned in hits inside `inner_hits` is relative to the `_nested` metadata. So in the above example only the comment part is returned per nested hit and not the entire source of the top level -document that contained the the comment. +document that contained the comment. [[hierarchical-nested-inner-hits]] ==== Hierarchical levels of nested object fields and inner hits. If a mapping has multiple levels of hierarchical nested object fields each level can be accessed via dot notated path. For example if there is a `comments` nested field that contains a `votes` nested field and votes should directly be returned -with the the root hits then the following path can be defined: +with the root hits then the following path can be defined: [source,js] -------------------------------------------------- diff --git a/docs/reference/search/search-template.asciidoc b/docs/reference/search/search-template.asciidoc index 76262644208..facdcf904b8 100644 --- a/docs/reference/search/search-template.asciidoc +++ b/docs/reference/search/search-template.asciidoc @@ -236,7 +236,7 @@ GET /_search/template } ------------------------------------------ -<1> Name of the the query template in `config/scripts/`, i.e., `storedTemplate.mustache`. +<1> Name of the query template in `config/scripts/`, i.e., `storedTemplate.mustache`. You can also register search templates by storing it in the elasticsearch cluster in a special index named `.scripts`. There are REST APIs to manage these indexed templates. @@ -297,7 +297,7 @@ GET /_search/template } } ------------------------------------------ -<1> Name of the the query template stored in the `.scripts` index. +<1> Name of the query template stored in the `.scripts` index. [float] ==== Validating templates diff --git a/docs/reference/search/suggesters/term-suggest.asciidoc b/docs/reference/search/suggesters/term-suggest.asciidoc index 965a487e293..ff5cd38cf21 100644 --- a/docs/reference/search/suggesters/term-suggest.asciidoc +++ b/docs/reference/search/suggesters/term-suggest.asciidoc @@ -111,9 +111,9 @@ doesn't take the query into account that is part of request. `string_distance`:: Which string distance implementation to use for comparing how similar - suggested terms are. Five possible values can be specfied: + suggested terms are. Five possible values can be specified: `internal` - The default based on damerau_levenshtein but highly optimized - for comparing string distancee for terms inside the index. + for comparing string distance for terms inside the index. `damerau_levenshtein` - String distance algorithm based on Damerau-Levenshtein algorithm. `levenstein` - String distance algorithm based on Levenstein edit distance diff --git a/docs/reference/setup/as-a-service.asciidoc b/docs/reference/setup/as-a-service.asciidoc index 1bd6d9bb7ae..3551571b386 100644 --- a/docs/reference/setup/as-a-service.asciidoc +++ b/docs/reference/setup/as-a-service.asciidoc @@ -75,7 +75,7 @@ sudo service elasticsearch start [float] ==== Using systemd -Distributions like Debian Jessie, Ubuntu 14, and many of the SUSE derivitives do not use the `chkconfig` tool to register services, but rather `systemd` and its command `/bin/systemctl` to start and stop services (at least in newer versions, otherwise use the `chkconfig` commands above). The configuration file is also placed at `/etc/sysconfig/elasticsearch` if the system is rpm based and `/etc/default/elasticsearch` if it is deb. After installing the RPM, you have to change the systemd configuration and then start up elasticsearch +Distributions like Debian Jessie, Ubuntu 14, and many of the SUSE derivatives do not use the `chkconfig` tool to register services, but rather `systemd` and its command `/bin/systemctl` to start and stop services (at least in newer versions, otherwise use the `chkconfig` commands above). The configuration file is also placed at `/etc/sysconfig/elasticsearch` if the system is rpm based and `/etc/default/elasticsearch` if it is deb. After installing the RPM, you have to change the systemd configuration and then start up elasticsearch [source,sh] -------------------------------------------------- diff --git a/docs/reference/setup/configuration.asciidoc b/docs/reference/setup/configuration.asciidoc index 2332e973dee..e4c79fc6582 100644 --- a/docs/reference/setup/configuration.asciidoc +++ b/docs/reference/setup/configuration.asciidoc @@ -133,7 +133,7 @@ request: curl http://localhost:9200/_nodes/process?pretty -------------- -If you see that `mlockall` is `false`, then it means that the the `mlockall` +If you see that `mlockall` is `false`, then it means that the `mlockall` request has failed. The most probable reason, on Linux/Unix systems, is that the user running Elasticsearch doesn't have permission to lock memory. This can be granted by running `ulimit -l unlimited` as `root` before starting Elasticsearch.