zhujiawen12345 opened a new issue #2357:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2357


   
长稳测试中,每个整点都会出现接口响应时延上升,490的情况,看下了日志,业务日志中正常响应时延都在20ms内,cse日志中时延较长,还出现没有状态码响应情况,
   5a58c558-0d59-4b8b-8309-9833dc4541c9|2021-04-21 
01:01:05.075|10.31.11.97|"POST /***/v1/****HTTP/1.1"|-|2
   
   不知道是否跟下面报错有关
   2021-04-21 00:01:07.090 [vert.x-eventloop-thread-3] WARN  - 
[HttpStatusItem.java:getFormattedItem:40] - 
[98e5b070-ccd1-434e-8f79-d199bc701577] - Response is closed before sending any 
data. Please check idle connection timeout for provider is properly configured.
   2021-04-21 00:01:14.637 [config-center-vert.x-eventloop-thread-0] ERROR - 
[ConfigCenterClient.java:lambda$null$10:415] - [] - Config update from 
https://10.33.26.147:30103 failed.
   2021-04-21 00:01:14.637 [config-center-vert.x-eventloop-thread-0] ERROR - 
[ConfigCenterClient.java:lambda$null$9:411] - [] - Server error message is 
[{"error_code":"SVCSTG.00300605","error_message":"java.util.concurrent.ExecutionException:
 io.grpc.StatusRuntimeException: UNAVAILABLE: Keepalive failed. The connection 
is likely gone"}].
   2021-04-21 00:01:27.267 [config-center-vert.x-eventloop-thread-0] ERROR - 
[ConfigCenterClient.java:lambda$null$10:415] - [] - Config update from 
https://10.33.26.147:30103 failed.
   2021-04-21 00:01:27.267 [config-center-vert.x-eventloop-thread-0] ERROR - 
[ConfigCenterClient.java:lambda$null$9:411] - [] - Server error message is 
[{"error_code":"SVCSTG.00300605","error_message":"java.util.concurrent.ExecutionException:
 io.grpc.StatusRuntimeException: UNAVAILABLE: io exception"}].
   2021-04-21 00:01:32.767 [Service Center Task 
[java.util.concurrent.ThreadPoolExecutor$Worker@35771602[State = -1, empty 
queue][171]]] WARN  - 
[MicroserviceInstanceStatusSyncTask.java:queryMicroserviceInstance:86] - [] - 
failed to find this instance in sc, waiting for instance registration
   2021-04-21 00:01:32.767 [Service Center Task 
[java.util.concurrent.ThreadPoolExecutor$Worker@35771602[State = -1, empty 
queue][171]]] WARN  - [ServiceCenterTaskMonitor.java:endCycle:51] - [] - sc 
task taken more than 3559ms to execute
   2021-04-21 00:01:32.769 [Service Center Task 
[java.util.concurrent.ThreadPoolExecutor$Worker@366c2d9c[State = -1, empty 
queue][172]]] ERROR - [AbstractServiceRegistry.java:findServiceInstances:244] - 
[] - Can not find any instances from service center due to previous errors. 
service=***/******/0.0.0+
   2021-04-21 00:01:39.212 [Service Center Task 
[java.util.concurrent.ThreadPoolExecutor$Worker@35771602[State = -1, empty 
queue][171]]] ERROR - [MicroserviceInstanceHeartbeatTask.java:heartbeat:79] - 
[] - Update heartbeat to service center failed, microservice 
instance=69de3bde6e22a23fe7afb632865c822e7382832f/403e3ccca1ba11eb87b6fa163e17e859
 does not exist
   2021-04-21 00:01:39.220 [Service Center Task 
[java.util.concurrent.ThreadPoolExecutor$Worker@35771602[State = -1, empty 
queue][171]]] WARN  - 
[MicroserviceInstanceStatusSyncTask.java:queryMicroserviceInstance:86] - [] - 
failed to find this instance in sc, waiting for instance registration
   2021-04-21 00:01:49.241 [Service Center Task 
[java.util.concurrent.ThreadPoolExecutor$Worker@35771602[State = -1, empty 
queue][171]]] WARN  - 
[MicroserviceInstanceStatusSyncTask.java:queryMicroserviceInstance:86] - [] - 
failed to find this instance in sc, waiting for instance registration
   2021-04-21 00:02:08.504 [vert.x-eventloop-thread-6] WARN  - 
[HttpStatusItem.java:getFormattedItem:40] - 
[98d3d511-7e2a-42fe-9540-9e21f0798779] - Response is closed before sending any 
data. Please check idle connection timeout for provider is properly configured.
   2021-04-21 00:02:58.102 [vert.x-eventloop-thread-10] WARN  - 
[HttpStatusItem.java:getFormattedItem:40] - 
[32be53ab-a2b5-4d97-8e65-5b7500bb0abd] - Response is closed before sending any 
data. Please check idle connection timeout for provider is properly configured.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to