# \#elasticsearch

**URL:** https://discuss.elastic.co/tag/elasticsearch/66.md

[Latest](https://discuss.elastic.co/latest.md) · [Categories](https://discuss.elastic.co/categories.md) · [Tags](https://discuss.elastic.co/tags.md)

---

## [Approaches to deal with "Limit of total fields \[1000\] in index has been exceeded"](https://discuss.elastic.co/t/approaches-to-deal-with-limit-of-total-fields-1000-in-index-has-been-exceeded/241039)

<div class="topic-metadata">

**Author:** [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Replies:** 1\
**Last updated:** [July 25, 2022, 11:52pm UTC](https://discuss.elastic.co/t/approaches-to-deal-with-limit-of-total-fields-1000-in-index-has-been-exceeded/241039 "2022-07-25T23:52:52Z")

</div>

This is a common warning seen due to what is commonly known as a mapping explosion. The docs go into this is more detail, but quickly (emphasis by the author); Defining too many fields in an index can lead to a mapping…

---

## [Can't get text on a START\_OBJECT](https://discuss.elastic.co/t/cant-get-text-on-a-start-object/244340)

<div class="topic-metadata">

**Author:** [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Replies:** 1\
**Last updated:** [June 1, 2022, 11:18pm UTC](https://discuss.elastic.co/t/cant-get-text-on-a-start-object/244340 "2022-06-01T23:18:06Z")

</div>

This error will be logged when Elasticsearch tries to index data that is an object, into a field that is not mapped as one. Or in reverse, if you try to index something that isn't an object into a field that is mapped as…

---

## [How do I size my cluster?](https://discuss.elastic.co/t/how-do-i-size-my-cluster/249483)

<div class="topic-metadata">

**Author:** [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Replies:** 0\
**Last updated:** [September 22, 2020, 8:56am UTC](https://discuss.elastic.co/t/how-do-i-size-my-cluster/249483 "2020-09-22T08:56:06Z")

</div>

The ultimate answer is the 42 of IT aka It depends. Let's break this down and see, which factors come into play. It's rather hard to give exact advice here, as many factors come into play Your indexing load, how many …

---

## [How to retrieve all unique values from a given field](https://discuss.elastic.co/t/how-to-retrieve-all-unique-values-from-a-given-field/247312)

<div class="topic-metadata">

**Author:** [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Replies:** 0\
**Last updated:** [September 3, 2020, 1:43am UTC](https://discuss.elastic.co/t/how-to-retrieve-all-unique-values-from-a-given-field/247312 "2020-09-03T01:43:37Z")

</div>

The quickest way to do this is to run a zero size, terms aggregation on the field. Using the Kibana sample log data set as an example, you would run; GET kibana\_sample\_data\_logs/\_search { "size": "0", "aggs": { …

---

## [Is it safe to expose Elasticsearch to the Internet?](https://discuss.elastic.co/t/is-it-safe-to-expose-elasticsearch-to-the-internet/247041)

<div class="topic-metadata">

**Author:** [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Replies:** 0\
**Last updated:** [September 1, 2020, 5:29am UTC](https://discuss.elastic.co/t/is-it-safe-to-expose-elasticsearch-to-the-internet/247041 "2020-09-01T05:29:47Z")

</div>

TLDR - Elasticsearch is not designed to be exposed to the internet. To dig into this with more detail, here's more information taken from this topic. This page in the docs says: NOTE: Elasticsearch installations are …

---

## [Why am I seeing a "FORBIDDEN/12/index read-only / allow delete" response against my index?](https://discuss.elastic.co/t/why-am-i-seeing-a-forbidden-12-index-read-only-allow-delete-response-against-my-index/244344)

<div class="topic-metadata">

**Author:** [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Replies:** 0\
**Last updated:** [August 10, 2020, 6:25am UTC](https://discuss.elastic.co/t/why-am-i-seeing-a-forbidden-12-index-read-only-allow-delete-response-against-my-index/244344 "2020-08-10T06:25:16Z")

</div>

You will usually see this error when your node(s) reach their flood stage disk level. When Elasticsearch detects a node's disk is nearing being full, it sets any index that the node holds to a read only state to protect…

---

## [CircuitBreakingException - Data too large](https://discuss.elastic.co/t/circuitbreakingexception-data-too-large/243633)

<div class="topic-metadata">

**Author:** [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Replies:** 0\
**Last updated:** [August 4, 2020, 1:16am UTC](https://discuss.elastic.co/t/circuitbreakingexception-data-too-large/243633 "2020-08-04T01:16:19Z")

</div>

Following on from this topic, we've extracted and expanded on this excellent explanation from @HenningAndersen. Seeing an error like this means that Elasticsearch prevented a request from executing to avoid an out of me…

---

## [How do I increase or reduce the shard count of an existing index?](https://discuss.elastic.co/t/how-do-i-increase-or-reduce-the-shard-count-of-an-existing-index/242704)

<div class="topic-metadata">

**Author:** [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Replies:** 0\
**Last updated:** [July 27, 2020, 7:37am UTC](https://discuss.elastic.co/t/how-do-i-increase-or-reduce-the-shard-count-of-an-existing-index/242704 "2020-07-27T07:37:17Z")

</div>

Traditionally, once you created an index with a given number of primary shards, it was set until you reindexed your data. That meant that if you hit the limit of documents in a shard, you might have been caught in a bit …

---

## [Pagination, Deep pagination and extraction of data](https://discuss.elastic.co/t/pagination-deep-pagination-and-extraction-of-data/238625)

<div class="topic-metadata">

**Author:** [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Replies:** 0\
**Last updated:** [June 25, 2020, 8:58am UTC](https://discuss.elastic.co/t/pagination-deep-pagination-and-extraction-of-data/238625 "2020-06-25T08:58:23Z")

</div>

When you want to get more results than the default 10 first, you can use: the size and from parameters to display by default up to 10000 records to your users. If you want to change this limit, you can change index.max…

---

## [Composite aggregations and pagination](https://discuss.elastic.co/t/composite-aggregations-and-pagination/240268)

<div class="topic-metadata">

**Author:** [@xeraa](https://discuss.elastic.co/u/xeraa)\
**Replies:** 0\
**Last updated:** [July 8, 2020, 6:10am UTC](https://discuss.elastic.co/t/composite-aggregations-and-pagination/240268 "2020-07-08T06:10:33Z")

</div>

Here's an example on how to do forward and reverse pagination with a composite aggregation. Example data, for use in Kibana's Dev Tools: POST test/\_doc { "date": "2020-01-01", "product": "a" } POST test/\_doc { "d…

---

## [What are ports 9200 and 9300 used for?](https://discuss.elastic.co/t/what-are-ports-9200-and-9300-used-for/238578)

<div class="topic-metadata">

**Author:** [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Replies:** 0\
**Last updated:** [June 25, 2020, 12:51am UTC](https://discuss.elastic.co/t/what-are-ports-9200-and-9300-used-for/238578 "2020-06-25T00:51:06Z")

</div>

\[This is an extension on an older thread - Elasticsearch port 9200 or 9300?\] By default, Elasticsearch uses two ports to listen to external TCP traffic; Port 9200 is used for all API calls over HTTP. This includes se…

---

## [Should I increase my threadpool size if I get rejected executions or HTTP 429 responses?](https://discuss.elastic.co/t/should-i-increase-my-threadpool-size-if-i-get-rejected-executions-or-http-429-responses/241044)

<div class="topic-metadata">

**Author:** [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Replies:** 0\
**Last updated:** [July 14, 2020, 2:23am UTC](https://discuss.elastic.co/t/should-i-increase-my-threadpool-size-if-i-get-rejected-executions-or-http-429-responses/241044 "2020-07-14T02:23:13Z")

</div>

Threadpools are described in the documentation as; A node uses several thread pools to manage memory consumption. Queues associated with many of the thread pools enable pending requests to be held instead of discarded. …
