# Getting issue during running a api command

**URL:** <https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142>\
**Category:** Elasticsearch\
**Created:** [November 25, 2021, 8:49am UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142 "2021-11-25T08:49:12Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Linuxuser](https://avatars.discourse-cdn.com/v4/letter/l/f475e1/32.png) [@Linuxuser](https://discuss.elastic.co/u/Linuxuser)\
**Post date:** [November 25, 2021, 8:49am UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/1 "2021-11-25T08:49:12Z")

</div>

[http://192.168.1.211:9000/api/sources?range=36000&size=5000](http://192.168.1.211:9000/api/sources?range=36000&size=5000)  
By running this command getting issue.

"ElasticsearchException{message=Unable to perform search query\n\n[parent] Data too large, data for [\<transport\_request\>] would be [11946545236/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=901/901b, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946578116/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=33781/32.9kb, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946578116/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=33781/32.9kb, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946562577/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=18242/17.8kb, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946561676/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=17341/16.9kb, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946545236/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=17341/16.9kb, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946578116/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=33781/32.9kb, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946545236/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=901/901b, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946578116/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=33781/32.9kb, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946561676/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=17341/16.9kb, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946561676/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=17341/16.9kb, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946545236/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=901/901b, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946545236/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=901/901b, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946545236/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=901/901b, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946545236/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b,

---

<div class="post-metadata">

**Author:** ![DineshNaik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dineshnaik/32/89308_2.png) [@DineshNaik](https://discuss.elastic.co/u/DineshNaik)\
**Post date:** [November 25, 2021, 12:46pm UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/2 "2021-11-25T12:46:28Z")

</div>

The error message itself is quite clear:

ElasticsearchException{message=**Unable to perform search query\n\n[parent] Data too large, data for [\<transport\_request\>] would be [11946545236/11.1gb], which is larger than the limit of [11946544332/11.1gb]**

You need to use smaller values for size , try say 100 or 500 instead of 5000 and see if it works

---

<div class="post-metadata">

**Author:** ![DineshNaik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dineshnaik/32/89308_2.png) [@DineshNaik](https://discuss.elastic.co/u/DineshNaik)\
**Post date:** [November 30, 2021, 2:53pm UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/3 "2021-11-30T14:53:53Z")

</div>

@Linuxuser Did you try with a smaller size? Let us know if you still getting the error.

---

<div class="post-metadata">

**Author:** ![Linuxuser](https://avatars.discourse-cdn.com/v4/letter/l/f475e1/32.png) [@Linuxuser](https://discuss.elastic.co/u/Linuxuser)\
**Post date:** [December 2, 2021, 5:21am UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/4 "2021-12-02T05:21:19Z")

</div>

@DineshNaik Sorry for the late reply i was out of town.  
I am getting the same issue.

{"type":"ApiError","message":"ElasticsearchException{message=Unable to perform search query\n\n[parent] Data too large, data for [\<transport\_request\>] would be [11946545236/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=901/901b, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946561676/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages [request=0/0b, fielddata=210765501/201mb, in\_flight\_requests=17341/16.9kb, accounting=11735778834/10.9gb][parent] Data too large, data for [\<transport\_request\>] would be [11946578116/11.1gb], which is larger than the limit of [11946544332/11.1gb], usages

Also getting the elastic status is red.

---

<div class="post-metadata">

**Author:** ![DineshNaik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dineshnaik/32/89308_2.png) [@DineshNaik](https://discuss.elastic.co/u/DineshNaik)\
**Post date:** [December 2, 2021, 7:45am UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/5 "2021-12-02T07:45:42Z")

</div>

Ok , fixing the cluster status would be the first step.

Check the cluster status and try to make it green first.  
you can use these commands to get an idea of what's going in the cluster.

curl -XGET "[http://localhost:9200/\_cluster/stats](http://localhost:9200/_cluster/stats)"  
curl -XGET "[http://localhost:9200/\_cat/shards](http://localhost:9200/_cat/shards)"  
curl -XGET "[http://localhost:9200/\_nodes/hot\_threads](http://localhost:9200/_nodes/hot_threads)"  
curl -XGET "[http://localhost:9200/\_cat/nodes](http://localhost:9200/_cat/nodes)"  
curl -XGET "[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)"

please read the below post to know more about this issue:

> [@What does this error mean - Data too large, data for \[\<transport\_request\>\]](https://discuss.elastic.co/t/what-does-this-error-mean-data-too-large-data-for-transport-request/209345/3):
>
> Hello @HenningAndersen, thank you for reply, but unfortunately setting: InitiatingHeapOccupancyPercent=30 ReservePercent=25 didn't help. I've also increased heap from 30G to 50G, but it doesn't help too: Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] Data too large, data for [\<transport\_request\>] would be [53028227584/49.3gb], which is larger than the limit of [51002736640/47.5gb], real usage: [53028224688/49.3gb], new bytes reserved: [2896/2.8kb] And I sti…

And this page to diagnose further:  
: [Fix common cluster issues | Elasticsearch Guide [7.14] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.14/fix-common-cluster-issues.html#circuit-breaker-errors)

---

<div class="post-metadata">

**Author:** ![Linuxuser](https://avatars.discourse-cdn.com/v4/letter/l/f475e1/32.png) [@Linuxuser](https://discuss.elastic.co/u/Linuxuser)\
**Post date:** [December 2, 2021, 9:43am UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/6 "2021-12-02T09:43:15Z")

</div>

1. curl -XGET "[http://localhost:9200/\_cluster/stats](http://localhost:9200/_cluster/stats)"  
output:

{"\_nodes":{"total":2,"successful":2,"failed":0},"cluster\_name":"graylog","cluster\_uuid":"zdnt0uYMR-Gz77tlPsmzMQ","timestamp":1638437591202,"status":"red","indices":{"count":404,"shards":{"total":1191,"primaries":1191,"replication":0.0,"index":{"shards":{"min":1,"max":3,"avg":2.948019801980198},"primaries":{"min":1,"max":3,"avg":2.948019801980198},"replication":{"min":0.0,"max":0.0,"avg":0.0}}},"docs":{"count":15794533747,"deleted":4608},"store":{"size\_in\_bytes":6983526621389},"fielddata":{"memory\_size\_in\_bytes":2023118460,"evictions":0},"query\_cache":{"memory\_size\_in\_bytes":0,"total\_count":1601,"hit\_count":0,"miss\_count":1601,"cache\_size":0,"cache\_count":0,"evictions":0},"completion":{"size\_in\_bytes":0},"segments":{"count":2319,"memory\_in\_bytes":12334309640,"terms\_memory\_in\_bytes":7913977192,"stored\_fields\_memory\_in\_bytes":4184825744,"term\_vectors\_memory\_in\_bytes":0,"norms\_memory\_in\_bytes":444928,"points\_memory\_in\_bytes":233055564,"doc\_values\_memory\_in\_bytes":2006212,"index\_writer\_memory\_in\_bytes":8340588,"version\_map\_memory\_in\_bytes":15194,"fixed\_bit\_set\_memory\_in\_bytes":0,"max\_unsafe\_auto\_id\_timestamp":-1,"file\_sizes":{}}},"nodes":{"count":{"total":2,"data":2,"coordinating\_only":0,"master":1,"ingest":2},"versions":["6.8.10","6.8.18"],"os":{"available\_processors":32,"allocated\_processors":32,"names":[{"name":"Linux","count":2}],"pretty\_names":[{"pretty\_name":"Ubuntu 16.04.7 LTS","count":1},{"pretty\_name":"Ubuntu 16.04.6 LTS","count":1}],"mem":{"total\_in\_bytes":67408044032,"free\_in\_bytes":2580172800,"used\_in\_bytes":64827871232,"free\_percent":4,"used\_percent":96}},"process":{"cpu":{"percent":7},"open\_file\_descriptors":{"min":2439,"max":4498,"avg":3468}},"jvm":{"max\_uptime\_in\_millis":1796489630,"versions":[{"version":"1.8.0\_252","vm\_name":"OpenJDK 64-Bit Server VM","vm\_version":"25.252-b09","vm\_vendor":"Private Build","count":1},{"version":"1.8.0\_292","vm\_name":"OpenJDK 64-Bit Server VM","vm\_version":"25.292-b10","vm\_vendor":"Private Build","count":1}],"mem":{"heap\_used\_in\_bytes":22818459960,"heap\_max\_in\_bytes":34132983808},"threads":349},"fs":{"total\_in\_bytes":13958664310784,"free\_in\_bytes":2358992531456,"available\_in\_bytes":1687792795648},"plugins":,"network\_types":{"transport\_types":{"security4":2},"http\_types":{"security4":2}}}}

1. curl -XGET "[http://localhost:9200/\_cat/shards](http://localhost:9200/_cat/shards)"  
output:

graylog\_232 2 r UNASSIGNED  
graylog\_232 0 p STARTED 6668518 3.4gb 172.20.17.47 DC-ELASTIC-01  
graylog\_232 0 r UNASSIGNED  
graylog\_232 0 r UNASSIGNED  
graylog\_160 1 p STARTED 94093797 59.2gb 172.20.24.163 DR-ELASTIC-01  
graylog\_160 1 r UNASSIGNED  
graylog\_160 1 r UNASSIGNED  
graylog\_160 2 p STARTED 94124970 59.3gb 172.20.24.163 DR-ELASTIC-01  
graylog\_160 2 r UNASSIGNED  
graylog\_160 2 r UNASSIGNED  
graylog\_160 0 p STARTED 94114348 59.3gb 172.20.24.163 DR-ELASTIC-01  
graylog\_160 0 r UNASSIGNED  
graylog\_160 0 r UNASSIGNED  
graylog\_330 1 p STARTED 6688107 2.1gb 172.20.17.47 DC-ELASTIC-01  
graylog\_330 1 r UNASSIGNED  
graylog\_330 1 r UNASSIGNED  
graylog\_330 2 p STARTED 6692207 2.1gb 172.20.17.47 DC-ELASTIC-01  
graylog\_330 2 r UNASSIGNED  
graylog\_330 2 r UNASSIGNED  
graylog\_330 0 p STARTED 6688802 2.1gb 172.20.17.47 DC-ELASTIC-01  
graylog\_330 0 r UNASSIGNED  
graylog\_330 0 r UNASSIGNED  
graylog\_436 1 p STARTED 6679283 2gb 172.20.17.47 DC-ELASTIC-01  
graylog\_436 1 r UNASSIGNED  
graylog\_436 1 r UNASSIGNED  
graylog\_436 2 p STARTED 6681739 2gb 172.20.17.47 DC-ELASTIC-01  
graylog\_436 2 r UNASSIGNED  
graylog\_436 2 r UNASSIGNED  
graylog\_436 0 p STARTED 6678108 2gb 172.20.17.47 DC-ELASTIC-01  
graylog\_436 0 r UNASSIGNED  
graylog\_436 0 r UNASSIGNED  
graylog\_235 1 p STARTED 6669703 3.3gb 172.20.24.163 DR-ELASTIC-01  
graylog\_235 1 r UNASSIGNED  
graylog\_235 1 r UNASSIGNED  
graylog\_235 2 p STARTED 6670671 3.3gb 172.20.24.163 DR-ELASTIC-01  
graylog\_235 2 r UNASSIGNED  
graylog\_235 2 r UNASSIGNED  
graylog\_235 0 p STARTED 6671232 3.3gb 172.20.24.163 DR-ELASTIC-01  
graylog\_235 0 r UNASSIGNED  
graylog\_235 0 r UNASSIGNED  
graylog\_452 1 p STARTED 6671516 2gb 172.20.17.47 DC-ELASTIC-01  
graylog\_452 1 r UNASSIGNED  
graylog\_452 1 r UNASSIGNED  
graylog\_452 2 p STARTED 6672535 2gb 172.20.17.47 DC-ELASTIC-01  
graylog\_452 2 r UNASSIGNED  
graylog\_452 2 r UNASSIGNED  
graylog\_452 0 p STARTED 6669030 2gb 172.20.17.47 DC-ELASTIC-01  
graylog\_452 0 r UNASSIGNED  
graylog\_452 0 r UNASSIGNED  
graylog\_429 1 p STARTED 6684044 1.8gb 172.20.17.47 DC-ELASTIC-01  
graylog\_429 1 r UNASSIGNED  
graylog\_429 1 r UNASSIGNED  
graylog\_429 2 p STARTED 6687401 1.8gb 172.20.17.47 DC-ELASTIC-01  
graylog\_429 2 r UNASSIGNED  
graylog\_429 2 r UNASSIGNED  
graylog\_429 0 p STARTED 6684144 1.8gb 172.20.17.47 DC-ELASTIC-01  
graylog\_429 0 r UNASSIGNED  
graylog\_429 0 r UNASSIGNED

1. curl -XGET "[http://localhost:9200/\_nodes/hot\_threads](http://localhost:9200/_nodes/hot_threads)"  
output:

::: {DC-ELASTIC-01}{GtMH3ewUQDaF6Xb4V6vHbg}{vEz4TtNlT2i9qnxS50kPeQ}{172.20.17.47}{172.20.17.47:9300}{ml.machine\_memory=33704022016, xpack.installed=true, ml.max\_open\_jobs=20, ml.enabled=true}  
Hot threads at 2021-12-02T09:37:57.101Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true:

::: {DR-ELASTIC-01}{VcirmtS6SBGRhWBDycXAVw}{kSKZM06XSL-XjFehLbECbg}{172.20.24.163}{172.20.24.163:9300}{ml.machine\_memory=33704022016, ml.max\_open\_jobs=20, xpack.installed=true, ml.enabled=true}  
Hot threads at 2021-12-02T09:37:57.128Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true:

```
2.4% (11.8ms out of 500ms) cpu usage by thread 'elasticsearch[DR-ELASTIC-01][transport_worker][T#8]'
 2/10 snapshots sharing following 48 elements
   java.lang.Throwable.fillInStackTrace(Native Method)
   java.lang.Throwable.fillInStackTrace(Throwable.java:784)
   java.lang.Throwable.<init>(Throwable.java:288)
   java.lang.Exception.<init>(Exception.java:84)
   java.lang.RuntimeException.<init>(RuntimeException.java:80)
   java.lang.IllegalArgumentException.<init>(IllegalArgumentException.java:72)
   org.elasticsearch.common.io.stream.StreamInput.readException(StreamInput.java:826)
   org.elasticsearch.ElasticsearchException.<init>(ElasticsearchException.java:137)
   org.elasticsearch.index.mapper.MapperException.<init>(MapperException.java:29)
   org.elasticsearch.index.mapper.MapperParsingException.<init>(MapperParsingException.java:30)
   org.elasticsearch.ElasticsearchException$ElasticsearchExceptionHandle$$Lambda$1042/2090142523.apply(Unknown Source)
   org.elasticsearch.ElasticsearchException.readException(ElasticsearchException.java:306)
   org.elasticsearch.common.io.stream.StreamInput.readException(StreamInput.java:799)
   org.elasticsearch.action.bulk.BulkItemResponse$Failure.<init>(BulkItemResponse.java:239)
   org.elasticsearch.action.bulk.BulkItemResponse.readFrom(BulkItemResponse.java:495)
   org.elasticsearch.action.bulk.BulkItemResponse.readBulkItem(BulkItemResponse.java:468)
   org.elasticsearch.action.bulk.BulkShardResponse.readFrom(BulkShardResponse.java:73)
   org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase$1.read(TransportReplicationAction.java:886)
   org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase$1.read(TransportReplicationAction.java:881)
   org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.read(TransportService.java:1107)
   org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.read(TransportService.java:1094)
   org.elasticsearch.transport.TcpTransport.handleResponse(TcpTransport.java:970)
   org.elasticsearch.transport.TcpTransport.messageReceived(TcpTransport.java:952)
   org.elasticsearch.transport.TcpTransport.inboundMessage(TcpTransport.java:763)
   org.elasticsearch.transport.netty4.Netty4MessageChannelHandler.channelRead(Netty4MessageChannelHandler.java:53)
   io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
   io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
   io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
   io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:323)
   io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:297)
   io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
   io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
   io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
   io.netty.handler.logging.LoggingHandler.channelRead(LoggingHandler.java:241)
   io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
   io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
   io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
   io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
   io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
   io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
   io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
   io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
   io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:656)
   io.netty.channel.nio.NioEventLoop.processSelectedKeysPlain(NioEventLoop.java:556)
   io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:510)
   io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:470)
   io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:909)
   java.lang.Thread.run(Thread.java:748)
 8/10 snapshots sharing following 2 elements
   io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:909)
   java.lang.Thread.run(Thread.java:748)

```

1. curl -XGET "[http://localhost:9200/\_cat/nodes](http://localhost:9200/_cat/nodes)"  
output:

172.20.17.47 58 96 3 0.59 0.67 0.59 mdi \* DC-ELASTIC-01  
172.20.24.163 75 96 4 1.08 0.91 0.77 di - DR-ELASTIC-01

1. curl -XGET "[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)"  
output:

{"cluster\_name":"graylog","status":"red","timed\_out":false,"number\_of\_nodes":2,"number\_of\_data\_nodes":2,"active\_primary\_shards":1191,"active\_shards":1191,"relocating\_shards":0,"initializing\_shards":0,"unassigned\_shards":2343,"delayed\_unassigned\_shards":0,"number\_of\_pending\_tasks":0,"number\_of\_in\_flight\_fetch":0,"task\_max\_waiting\_in\_queue\_millis":0,"active\_shards\_percent\_as\_number":33.70118845500849}

These are the outputs of the given command kindly take a look and tell me what can i change to make it green.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 2, 2021, 10:47am UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/7 "2021-12-02T10:47:53Z")

</div>

Your two data nodes are not running exactly the same version, which prevents primary shards on the newer node to replicate to the older one. Upgrade the older node to exactly the same version as the newer node and I suspect you will see replicas getting allocated.

---

<div class="post-metadata">

**Author:** ![Linuxuser](https://avatars.discourse-cdn.com/v4/letter/l/f475e1/32.png) [@Linuxuser](https://discuss.elastic.co/u/Linuxuser)\
**Post date:** [December 2, 2021, 1:20pm UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/8 "2021-12-02T13:20:40Z")

</div>

you mean there is difference in Elasticsearch version?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 2, 2021, 1:30pm UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/9 "2021-12-02T13:30:46Z")

</div>

Yes.

"versions":["6.8.10","6.8.18"]

---

<div class="post-metadata">

**Author:** ![Linuxuser](https://avatars.discourse-cdn.com/v4/letter/l/f475e1/32.png) [@Linuxuser](https://discuss.elastic.co/u/Linuxuser)\
**Post date:** [December 2, 2021, 1:36pm UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/10 "2021-12-02T13:36:20Z")

</div>

thanks to guide i will do the same as you told and then i will inform you.

---

<div class="post-metadata">

**Author:** ![DineshNaik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dineshnaik/32/89308_2.png) [@DineshNaik](https://discuss.elastic.co/u/DineshNaik)\
**Post date:** [December 2, 2021, 1:44pm UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/11 "2021-12-02T13:44:10Z")

</div>

@Linuxuser you can quickly verify the same running  
`curl localhost:9200` on both nodes .

As @Christian_Dahlqvist rightly said you need to have the same version in both nodes/vm's .

Also having 1000's of shard per vm is not a very good idea unless you have done thorough performance testing.

Remember that there is an additional cost for each shard that you allocate:

- Since a shard is essentially a Lucene index, it consumes file handles, memory, and CPU resources. Although many small shards can speed up processing per shard, they may also form query queues that compromise the cluster performance and decrease query throughput.

- Each search request will touch a copy of every shard in the index, which isn’t a problem when the shards are spread across several nodes. However, contention arises and performance decreases when the shards are competing for the same hardware resources.

Try to bring up the cluster to green status and then look for the optimizations.

---

<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 30, 2021, 1:44pm UTC](https://discuss.elastic.co/t/getting-issue-during-running-a-api-command/290142/12 "2021-12-30T13:44:19Z")

</div>

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