# Unsupported config option for services.elastic-1: 'processors'

**URL:** <https://discuss.elastic.co/t/unsupported-config-option-for-services-elastic-1-processors/106395>\
**Category:** Elasticsearch\
**Created:** [November 5, 2017, 1:26am UTC](https://discuss.elastic.co/t/unsupported-config-option-for-services-elastic-1-processors/106395 "2017-11-05T01:26:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![grantcurell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grantcurell/32/23813_2.png) [@grantcurell](https://discuss.elastic.co/u/grantcurell)\
**Post date:** [November 5, 2017, 1:26am UTC](https://discuss.elastic.co/t/unsupported-config-option-for-services-elastic-1-processors/106395/1 "2017-11-05T01:26:35Z")

</div>

I'm setting up three nodes in a docker compose file to run on a single (beefy) host. I'm following the practices outlined in the following places:

> **[Install Elasticsearch with Docker | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html)**

> [@Can I run multiple Elasticsearch nodes on the same machine?](https://discuss.elastic.co/t/can-i-run-multiple-elasticsearch-nodes-on-the-same-machine/67):
>
> We generally recommend scaling horizontally by adding small/medium machines. But we do have a few customers with big machines (eg. 512 RAM, 256 cores, etc..) who have deployed multiple Elasticsearch nodes per big machine. There are some caveats and recommendations if you choose this deployment architecture: Max heap size for each node instance should be \< 32Gb. This is because a heap size above 32Gb will actually be counterproductive for the JVM will stop compressing pointers ([https://wikis…](https://wikis.oracle.com/display/HotSpotInternals/CompressedOops)

> **[Thread pools | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-threadpool.html#processors)**

Below is the snippet of my docker compose file causing me issues.

* * *

version: '2'  
services:  
elastic-1:  
image: "elasticsearch:latest"  
restart: "always"  
networks:  
- elastic-backend  
ports:  
- "9200:9200"  
volumes:  
- "PPINSTALLPP/var/elastic:/usr/share/elasticsearch/data/node1"  
environment:  
- "ES\_JAVA\_OPTS=-Xms2G -Xmx2G"  
- cluster.name=elasticsearch  
- node.name=elastic-1  
- xpack.security.enabled=false

```
  # This option keeps JVM memory from being paged out to swap
  - bootstrap.memory_lock=true

  - discovery.zen.ping.multicast.enabled=false
  - discovery.zen.ping.unicast.hosts="elastic-2","elastic-3"

ulimits:
  memlock:
    soft: -1
    hard: -1

# This caps the amount of memory available to the container
mem_limit: 2g

processors: 2

```

* * *

Note: I've tuned the resources way down just for testing.

I want to set the number of processors so I don't have all three instances competing on the same processors. I receive the following error:

Unsupported config option for services.elastic-1: 'processors'

I'm not sure what I'm missing. Any ideas?

---

<div class="post-metadata">

**Author:** ![grantcurell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grantcurell/32/23813_2.png) [@grantcurell](https://discuss.elastic.co/u/grantcurell)\
**Post date:** [November 7, 2017, 8:10pm UTC](https://discuss.elastic.co/t/unsupported-config-option-for-services-elastic-1-processors/106395/2 "2017-11-07T20:10:29Z")

</div>

Bump - does the processors option no longer work?

---

<div class="post-metadata">

**Author:** ![grantcurell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grantcurell/32/23813_2.png) [@grantcurell](https://discuss.elastic.co/u/grantcurell)\
**Post date:** [November 7, 2017, 9:46pm UTC](https://discuss.elastic.co/t/unsupported-config-option-for-services-elastic-1-processors/106395/3 "2017-11-07T21:46:46Z")

</div>

I figured it out. You have to put it under the environment header like:

elastic-#:  
....  
environment:  
- processors=2  
...

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 5, 2017, 9:47pm UTC](https://discuss.elastic.co/t/unsupported-config-option-for-services-elastic-1-processors/106395/4 "2017-12-05T21:47:11Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.