# Having issues with more than 1 instance

**URL:** https://discuss.elastic.co/t/having-issues-with-more-than-1-instance/207154
**Category:** Elastic Cloud on Kubernetes (ECK)
**Created:** [November 8, 2019, 5:21pm UTC](https://discuss.elastic.co/t/having-issues-with-more-than-1-instance/207154 "2019-11-08T17:21:45Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![booboothefool](https://avatars.discourse-cdn.com/v4/letter/b/2bfe46/32.png) [@booboothefool](https://discuss.elastic.co/u/booboothefool)
#### Post date: [November 8, 2019, 5:21pm UTC](https://discuss.elastic.co/t/having-issues-with-more-than-1-instance/207154/1 "2019-11-08T17:21:45Z")

</div>

Hi there so I've gotten the single instance configuration to work. And Kibana is able to connect to it.

```auto
apiVersion: elasticsearch.k8s.elastic.co/v1beta1
kind: Elasticsearch
metadata:
  name: elastic
spec:
  version: 7.4.2
  nodeSets:
    - name: default
      count: 1
      config:
        node.master: true
        node.data: true
        node.ingest: true
        node.store.allow_mmap: false
  http:
    tls:
      selfSignedCertificate:
        disabled: true

```

However as soon as I try to add more, in order to scale out reads e.g.:

```auto
apiVersion: elasticsearch.k8s.elastic.co/v1beta1
kind: Elasticsearch
metadata:
  name: elastic
spec:
  version: 7.4.2
  nodeSets:
    - name: default
      count: 3
      config:
        node.master: true
        node.data: true
        node.ingest: true
        node.store.allow_mmap: false
  http:
    tls:
      selfSignedCertificate:
        disabled: true

```

```auto
apiVersion: elasticsearch.k8s.elastic.co/v1beta1
kind: Elasticsearch
metadata:
  name: elastic
spec:
  version: 7.4.2
  nodeSets:
    - name: default
      count: 1
      config:
        node.master: true
        node.data: true
        node.ingest: true
        node.store.allow_mmap: false
    - name: data
      count: 2
      config:
        node.master: false
        node.data: true
        node.ingest: false
        node.store.allow_mmap: false
  http:
    tls:
      selfSignedCertificate:
        disabled: true

```

All of my Elasticsearch pods start crashing/erroring out, and Kibana is not able to connect. If I start with 1 Elasticsearch + 1 Kibana it is able to connect, then when I scale up to 3 Elasticsearch, the pods stay running but eventually Kibana shows everything in a red state and it no longer works. I am running on an 8 vCPU x 32GB mem + 4 vCPU x 16GB mem + 4 vCPU x 16GB mem, so I believe I have enough resources.

Any suggestions?

---

<div class="post-metadata">

### Author: ![Anya\_Sabo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anya_sabo/32/49903_2.png) [@Anya\_Sabo](https://discuss.elastic.co/u/Anya_Sabo)
#### Post date: [November 8, 2019, 9:16pm UTC](https://discuss.elastic.co/t/having-issues-with-more-than-1-instance/207154/2 "2019-11-08T21:16:00Z")

</div>

Can you share the logs of the ES pods when they crash? That should help diagnose what is happening. I used your original spec and then increased the count to 3 and it worked as expected. I then tried applying the extra nodeset over it as in your third example and it also worked.

---

<div class="post-metadata">

### Author: ![booboothefool](https://avatars.discourse-cdn.com/v4/letter/b/2bfe46/32.png) [@booboothefool](https://discuss.elastic.co/u/booboothefool)
#### Post date: [November 13, 2019, 9:30pm UTC](https://discuss.elastic.co/t/having-issues-with-more-than-1-instance/207154/4 "2019-11-13T21:30:05Z")

</div>

I was able to get another ES node up and it didn't crash, but I will provide logs if it does again.

However in my Kibana monitoring it still shows a yellow state, and only shows the original 1 node. It doesn't seem to be picking up the new node `elastic-es-default-1`.

```auto
elastic-es-default-0 Running
elastic-es-default-1 Running

```

I also noticed when I upgrade the count, it won't seem to go past 2. For example when I change to `count: 3` and re-apply the yaml, it stays at 2 pods and nothing happens, no errors.

And in the Kibana I am intermittently getting "Internal Server Error". It seems to happen quite frequently but will eventually fix itself if you keep refreshing.

```auto
SearchError: Internal Server Error
    at https://localhost:5601/bundles/commons.bundle.js:5:1843343
    at processQueue (https://localhost:5601/built_assets/dlls/vendors.bundle.dll.js:417:203810)
    at https://localhost:5601/built_assets/dlls/vendors.bundle.dll.js:417:204773
    at Scope.$digest (https://localhost:5601/built_assets/dlls/vendors.bundle.dll.js:417:214757)
    at Scope.$apply (https://localhost:5601/built_assets/dlls/vendors.bundle.dll.js:417:217761)
    at done (https://localhost:5601/built_assets/dlls/vendors.bundle.dll.js:417:136089)
    at completeRequest (https://localhost:5601/built_assets/dlls/vendors.bundle.dll.js:417:139882)
    at XMLHttpRequest.requestLoaded (https://localhost:5601/built_assets/dlls/vendors.bundle.dll.js:417:138624)

```

I am running on IBM Cloud Kubernetes. I don't see anything useful in any logs, but let me know if there's any specific info I can provide to help troubleshoot the issue.

---

<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: [November 4, 2022, 7:32am UTC](https://discuss.elastic.co/t/having-issues-with-more-than-1-instance/207154/5 "2022-11-04T07:32:41Z")

</div>


