[GitHub] [skywalking] wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task

2019-09-20 Thread GitBox
wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task URL: https://github.com/apache/skywalking/issues/3441#issuecomment-533441251 Really, there is nothing I can do. There are plenty of users using the project in production environments. Some of them

[GitHub] [skywalking] wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task

2019-09-20 Thread GitBox
wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task URL: https://github.com/apache/skywalking/issues/3441#issuecomment-533438779 Read `ElasticsearchStorageTTL`, if you will find the delete wouldn't happen in every 5 mins. This is only the check running

[GitHub] [skywalking] wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task

2019-09-20 Thread GitBox
wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task URL: https://github.com/apache/skywalking/issues/3441#issuecomment-533435504 > yes i will investigate our ES, but what i think is the data keeper should be the lowest priority task compare to others,

[GitHub] [skywalking] wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task

2019-09-19 Thread GitBox
wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task URL: https://github.com/apache/skywalking/issues/3441#issuecomment-533416580 If they are blocked, that is expected from design level, You need to find out why elasticsearch doesn't response. Check your

[GitHub] [skywalking] wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task

2019-09-15 Thread GitBox
wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task URL: https://github.com/apache/skywalking/issues/3441#issuecomment-531554608 In 6.4.0, we use our own thread pool. Because in some cases, too many grpc thread created. That is expected.

[GitHub] [skywalking] wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task

2019-09-14 Thread GitBox
wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task URL: https://github.com/apache/skywalking/issues/3441#issuecomment-531535556 That is new to me. Could you find why? How to make grpc thread exit

[GitHub] [skywalking] wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task

2019-09-14 Thread GitBox
wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task URL: https://github.com/apache/skywalking/issues/3441#issuecomment-531534862 What do you mean thread destoried? This is an automated

[GitHub] [skywalking] wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task

2019-09-14 Thread GitBox
wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task URL: https://github.com/apache/skywalking/issues/3441#issuecomment-531534825 They you have to look up your server env. Something blocks, I can't be sure why. Most likely, your storage crashed or facing

[GitHub] [skywalking] wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task

2019-09-09 Thread GitBox
wu-sheng commented on issue #3441: Grpc server thread pool is full, rejecting the task URL: https://github.com/apache/skywalking/issues/3441#issuecomment-529722735 We added thread size control to make sure you wouldn't OOM. But two many connections are not acceptable. You should not have