jular6759 opened a new issue #2191: listener timeout after waiting for [30000] 
ms java.io.IOException: listener timeout after waiting for [30000] ms
URL: https://github.com/apache/incubator-skywalking/issues/2191
 
 
   Please answer these questions before submitting your issue.
   
   - Why do you submit this issue?
   - [x] Question or discussion
   - [ ] Bug
   - [ ] Requirement
   - [ ] Feature or performance improvement
   
   ___
   ### Question
   - What do you want to know?
     When I start up collector server, I get "listener timeout after waiting 
for [30000] ms
   java.io.IOException: listener timeout after waiting for [30000] ms" error 
every five minute.Can I config some thing to avoid it? Thanks. The detail error 
messge as follow:
   
   2019-01-21 18:40:43,387 - 
org.apache.skywalking.oap.server.core.storage.ttl.DataTTLKeeperTimer - 122 
[pool-11-thread-1] WARN  [] - History of segment delete failure, time bucket 
20190121171009
   2019-01-21 18:40:43,387 - 
org.apache.skywalking.oap.server.core.storage.ttl.DataTTLKeeperTimer - 123 
[pool-11-thread-1] ERROR [] - listener timeout after waiting for [30000] ms
   java.io.IOException: listener timeout after waiting for [30000] ms
           at 
org.elasticsearch.client.RestClient$SyncResponseListener.get(RestClient.java:684)
 ~[elasticsearch-rest-client-6.3.2.jar:6.3.2]
           at 
org.elasticsearch.client.RestClient.performRequest(RestClient.java:235) 
~[elasticsearch-rest-client-6.3.2.jar:6.3.2]
           at 
org.elasticsearch.client.RestClient.performRequest(RestClient.java:198) 
~[elasticsearch-rest-client-6.3.2.jar:6.3.2]
           at 
org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient.delete(ElasticSearchClient.java:179)
 ~[library-client-6.0.0-beta.jar:6.0.0-beta]
           at 
org.apache.skywalking.oap.server.storage.plugin.elasticsearch.base.HistoryDeleteEsDAO.deleteHistory(HistoryDeleteEsDAO.java:40)
 ~[storage-elasticsearch-plugin-6.0.0-beta.jar:6.0.0-beta]
           at 
org.apache.skywalking.oap.server.core.storage.ttl.DataTTLKeeperTimer.execute(DataTTLKeeperTimer.java:119)
 ~[server-core-6.0.0-beta.jar:6.0.0-beta]
           at 
org.apache.skywalking.oap.server.core.storage.ttl.DataTTLKeeperTimer.lambda$delete$1(DataTTLKeeperTimer.java:99)
 ~[server-core-6.0.0-beta.jar:6.0.0-beta]
           at java.lang.Iterable.forEach(Iterable.java:75) ~[?:1.8.0_92]
           at 
org.apache.skywalking.oap.server.core.storage.ttl.DataTTLKeeperTimer.delete(DataTTLKeeperTimer.java:85)
 ~[server-core-6.0.0-beta.jar:6.0.0-beta]
           at 
org.apache.skywalking.apm.util.RunnableWithExceptionProtection.run(RunnableWithExceptionProtection.java:36)
 [apm-util-6.0.0-beta.jar:6.0.0-beta]
           at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[?:1.8.0_92]
           at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[?:1.8.0_92]
           at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [?:1.8.0_92]
           at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [?:1.8.0_92]
           at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[?:1.8.0_92]
           at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[?:1.8.0_92]
           at java.lang.Thread.run(Thread.java:745) [?:1.8.0_92]
   ___
   ### Bug
   - Which version of SkyWalking, OS and JRE?
     SkyWalking v6.0.0-beta, SUSE Linux Enterprise Server 11 (x86_64), java 
version "1.8.0_92"
   - Which company or project?
   
   - What happen?
   If possible, provide a way for reproducing the error. e.g. demo application, 
component version.
   
   ___
   ### Requirement or improvement
   - Please describe about your requirements or improvement suggestions.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to