# Visualize Request Timeout after 30000ms
**URL:** https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939
**Category:** Kibana
**Created:** [July 20, 2017, 12:59pm UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939 "2017-07-20T12:59:04Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@swatititame](https://discuss.elastic.co/u/swatititame)
#### Post date: [July 20, 2017, 12:59pm UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/1 "2017-07-20T12:59:04Z")
I am getting Visualize Request Timeout after 30000ms while loading dashboard in kibana.I increase requestTimeout.
elasticsearch.requestTimeout: 200000
After this I am not getting error in kibana but my dashboard fails to load and I am getting attached error Google chrome ran out of memory while trying to display this webpage.
.- 
Please suggest solution for same.
---
### Author:  [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)
#### Post date: [July 21, 2017, 12:31am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/2 "2017-07-21T00:31:09Z")
Hi there, I have a few questions to try to help me understand the problem better:
1. Which version of Kibana are you using?
2. Could you copy/paste the URL of the dashboard you're trying to load?
3. Could you take a look at [this issue](https://github.com/elastic/kibana/issues/7427) and tell me if it seems related?
Thanks,
CJ
---
### Author:  [@swatititame](https://discuss.elastic.co/u/swatititame)
#### Post date: [July 21, 2017, 5:16am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/3 "2017-07-21T05:16:28Z")
Hi CJ,
Thanks for took a look at my issue.
1.I am using kibana-4.5.4-windows,elasticsearch-2.3.5 ,logstash-5.0.0 and filebeat-5.2.2-windows-x86\_64.
2.[http://143.22.209.122:8080/SmartMonitoringAdv/sapapplicationadoptionK8P.html](http://143.22.209.122:8080/SmartMonitoringAdv/sapapplicationadoptionK8P.html)
3.I am looking in to issue which you attached.
You may not be able to open my dashboard Url because that is the client machine where i am running ELK and our machine needs to hook in to their environment.
Best regards,
Swati
---
### Author:  [@swatititame](https://discuss.elastic.co/u/swatititame)
#### Post date: [July 21, 2017, 7:00am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/4 "2017-07-21T07:00:51Z")
1.I use filebeat to read 3(defaultTrace\ __.trc,applications\__.log,security\_00._.log) different log file from 7 server.Volume of data is too high.
2.I am using elasticsearch to store data and parse data using logstash.
3.I have created 3(Application adoption,operation managemet,security audit) type of dashboard of each server and total 14 visualizations.
4.Each dashboard contain (4,5,5) visualizations respectively.
5.There are four sources (K8P,K2P,K2Q,K8Q).
6.K8P and K8Q's os is linux
7.K2P and K2Q rans on windows.
8.I have created separate index for K8P,K2P,K2Q,K8Q.
9.defaultTrace\ __.trc,applications\__.log this two files data collected in one common index.
10.security\_00._.log this files data collected in separate index.
11.Same index creation pattern follows for all sources.
12.Volume of data from K8P source is too high because it contains 3 servers and severs contains multiple node so large data is collecting in to index.
13.Fromat of data is same in all files.
14.Sample data
#2.0#2017 03 05 08:12:31:974#0-500#Warning#/System/Security/Authentication#
#BC-JAS-SEC#security#C0008F16D17A093700000001000042E0#29014150000000004#[sap.com/irj#com.sap.engine.services.security.authentication.logincontext.table#Guest#0##B3A03E0D01A411E7B69F000001BAB886#b3a03e0d01a411e7b69f000001bab886##0#Thread](http://sap.com/irj#com.sap.engine.services.security.authentication.logincontext.table#Guest#0##B3A03E0D01A411E7B69F000001BAB886#b3a03e0d01a411e7b69f000001bab886##0#Thread)[HTTP Worker [@979253619],5,Dedicated\_Application\_Thread]#Plain##
LOGIN.FAILED
User: N/A
IP Address: 143.22.209.122
Authentication Stack: ticket
Authentication Stack Properties:
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false true
#1 trusteddn1 = CN=GTA,O=Proctor and Gamble,C=NA
#2 trusteddn2 = CN=K2E,OU=J2EE
#3 trusteddn3 = CN=K2X,OU=J2EE
#4 trusteddn4 = OU=J2EE,CN=K2D
#5 trusteddn5 = CN=KAQ
#6 trusteddn6 = OU=J2EE,CN=GTD
#7 trusteddn7 = CN=KAQ
#8 trusteddn8 = CN=KAD
#9 trustediss1 = CN=GTA,O=Proctor and Gamble,C=NA
#10 trustediss2 = CN=K2E,OU=J2EE
#11 trustediss3 = CN=K2X,OU=J2EE
#12 trustediss4 = OU=J2EE,CN=K2D
#13 trustediss5 = CN=KAQ
#14 trustediss6 = OU=J2EE,CN=GTD
#15 trustediss7 = CN=KAQ
#16 trustediss8 = CN=KAD
#17 trustedsys1 = GTA,400
#18 trustedsys2 = K2E,000
#19 trustedsys3 = K2X,000
#20 trustedsys4 = K2D,000
#21 trustedsys5 = KAQ,000
#22 trustedsys6 = GTD,000
#23 trustedsys7 = KAQ,400
#24 trustedsys8 = KAD,400
#25 ume.configuration.active = true
2. com.cybersafe.sap.jaas.CSTBsapwaLoginModule OPTIONAL ok exception true Authorization header not found or malformed.
#1 Mode = standalone
#2 OutputUserNameFormat = user
#3 ServiceName = HTTP/bdc-bij002.na.pg.com@NA.PG.COM
3. com.sap.security.core.server.jaas.CreateTicketLoginModule SUFFICIENT ok false true
#1 ume.configuration.active = true
4. com.cybersafe.sap.jaas.CSTBsapwaKerberosLoginModule OPTIONAL ok false true
#1 ErrorWhenNoCreds = false
#2 Mode = standalone
#3 OutputUserNameFormat = user
5. com.sap.security.core.server.jaas.CreateTicketLoginModule SUFFICIENT ok false true
#1 ume.configuration.active = true
6. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok false false
7. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok false true
#1 ume.configuration.active = true
No logon policy was applied#
15.I am trying to load dashboard for 1 month [data.It](http://data.It) will not load.
16.particularly large field name is [ErrorMessage.It](http://ErrorMessage.It) conatins too large data as shown in sample.
17.Total fields
"#(?[^#]_)
#(?[^#]_)-yes
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)-yes
#(?[^#]_)
#(?[^#]_)-yes
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)
#(?[^#]_)-yes
#"}
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 21, 2017, 7:30am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/5 "2017-07-21T07:30:34Z")
It looks like your dashboard contains 2 visualisations showing unique (cardinality query) users over a month of data, which can be quite heavy. How much data do you have in the cluster? How many indices/shards? What is the specification of your Elasticsearch cluster? Does the dashboard work if you query a shorter time period?
---
### Author:  [@swatititame](https://discuss.elastic.co/u/swatititame)
#### Post date: [July 21, 2017, 7:42am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/6 "2017-07-21T07:42:49Z")
Yes ,Dashboard works for 1 week data.
this is my yml file.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 21, 2017, 7:45am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/7 "2017-07-21T07:45:27Z")
Then it looks like your Elasticsearch cluster is not powerful enough to serve that dashboard for such a longtime period with the current settings. You may want to scale up and/or out or potentially try to improve performance by optimising your sharding strategy.
---
### Author:  [@swatititame](https://discuss.elastic.co/u/swatititame)
#### Post date: [July 21, 2017, 7:46am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/8 "2017-07-21T07:46:53Z")
Could please let me know what configuartion is required for sharding strategy.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 21, 2017, 7:47am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/9 "2017-07-21T07:47:39Z")
> [@Christian\_Dahlqvist](#):
>
> How much data do you have in the cluster? How many indices/shards? What is the specification of your Elasticsearch cluster?
That is why I asked these questions.
---
### Author:  [@swatititame](https://discuss.elastic.co/u/swatititame)
#### Post date: [July 21, 2017, 7:48am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/10 "2017-07-21T07:48:10Z")
I tried to increase number of replicas in kibana but I lost all the indexes.I have to create new index.
---
### Author:  [@swatititame](https://discuss.elastic.co/u/swatititame)
#### Post date: [July 21, 2017, 7:49am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/11 "2017-07-21T07:49:35Z")
I didn't specify anything explicitly .It's default one.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 21, 2017, 10:28am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/12 "2017-07-21T10:28:26Z")
Why did you lose all the indices? What is the current status of the cluster? Still seeing the timeouts?
---
### Author:  [@swatititame](https://discuss.elastic.co/u/swatititame)
#### Post date: [July 22, 2017, 7:27am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/13 "2017-07-22T07:27:36Z")
No,Now I didnt't see timeout but I am not able to load 1 week or 1 month data in dashboard.
I can fetch 15 mins data efficiently.
It give me waiting popup . and after that it says google chrome ran out of memory. 
please let me know How I can load 1 month data quickly.
---
### Author:  [@swatititame](https://discuss.elastic.co/u/swatititame)
#### Post date: [July 24, 2017, 9:50am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/14 "2017-07-24T09:50:52Z")
cluster/health?pretty'
> {
> "cluster\_name": "elasticsearch",
> "status": "red",
> "timed\_out": false,
> "number\_of\_nodes": 1,
> "number\_of\_data\_nodes": 1,
> "active\_primary\_shards": 61,
> "active\_shards": 61,
> "relocating\_shards": 0,
> "initializing\_shards": 0,
> "unassigned\_shards": 121,
> "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.51648351648351
> }
indices
> health status index pri rep docs.count docs.deleted store.size pri.store.size
> yellow open sec-k8p-no-index 5 1 52597 0 88.9mb 88.9mb
> yellow open security-timeout-k8q 5 1 223688 0 174.7mb 174.7mb
> yellow open sap-security-logs-k2q 5 1 61754 0 80.1mb 80.1mb
> yellow open sap-trace-app-logs-k8q 5 1 71539 0 166.5mb 166.5mb
> yellow open sap-security-logs-k2p 5 1 15522 0 21.6mb 21.6mb
> red open sap-trace-app-logs-nprd-qa 5 2
> yellow open sap-trace-app-logs-k8p 5 1 19087974 0 34.8gb 34.8gb
> red open sap-trace-app-logs-prd 5 2
> yellow open .kibana 1 1 81 3 117.1kb 117.1kb
> red open sap-security-logs-nprd-qa 5 2
> yellow open sap-security-logs-k8q 5 1 11471 0 20.5mb 20.5mb
> yellow open sap-security-logs-k8p 5 1 12023344 0 12.1gb 12.1gb
> red open sap-security-logs-prd 5 2
> yellow open k8p-no-index 5 1 306750 0 501.8mb 501.8mb
> yellow open timeout-k8p 5 1 181864 0 300.4mb 300.4mb
> yellow open sap-trace-app-logs-k2q 5 1 37595 1 79.1mb 79.1mb
> yellow open sap-trace-app-logs-k2p 5 1 279188 0 729.3mb 729.3mb `
---
### Author:  [@swatititame](https://discuss.elastic.co/u/swatititame)
#### Post date: [August 1, 2017, 6:31am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/15 "2017-08-01T06:31:32Z")
Please suggest me some solution to load heavy data.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 29, 2017, 6:39am UTC](https://discuss.elastic.co/t/visualize-request-timeout-after-30000ms/93939/16 "2017-08-29T06:39:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.