qianglu1989 opened a new issue #3275: Can't find service by service instance id 
from cache, service instance id is: 152
URL: https://github.com/apache/skywalking/issues/3275
 
 
   英文不好,中文说下,异常如下,切换es集群了,为了方便数据没有迁移,会一直报下面的问题,怎么解决?
   
   
   
   
rg.apache.skywalking.oap.server.core.register.service.ServiceInstanceInventoryRegister
 - 108 [grpc-default-executor-24] WARN  [] - Service instance 956 heartbeat, 
but not found in storage.
   2019-08-16 14:32:41,008 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-83] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 152
   2019-08-16 14:32:41,008 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-75] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 956
   2019-08-16 14:32:41,009 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-44] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 902
   2019-08-16 14:32:41,009 - 
org.apache.skywalking.oap.server.receiver.register.provider.handler.v6.grpc.ServiceInstancePingServiceHandler
 - 68 [grpc-default-executor-24] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 956, will send a reset command 
to agent side
   2019-08-16 14:32:41,011 - 
org.apache.skywalking.oap.server.core.register.service.ServiceInstanceInventoryRegister
 - 108 [grpc-default-executor-85] WARN  [] - Service instance 902 heartbeat, 
but not found in storage.
   2019-08-16 14:32:41,012 - 
org.apache.skywalking.oap.server.receiver.register.provider.handler.v6.grpc.ServiceInstancePingServiceHandler
 - 68 [grpc-default-executor-85] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 902, will send a reset command 
to agent side
   2019-08-16 14:32:41,017 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-115] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 1029
   2019-08-16 14:32:41,017 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-75] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 33
   2019-08-16 14:32:41,032 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-66] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 501
   2019-08-16 14:32:41,034 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-114] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 295
   2019-08-16 14:32:41,034 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-85] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 1149
   2019-08-16 14:32:41,035 - 
org.apache.skywalking.oap.server.core.register.service.ServiceInstanceInventoryRegister
 - 108 [grpc-default-executor-114] WARN  [] - Service instance 295 heartbeat, 
but not found in storage.
   2019-08-16 14:32:41,036 - 
org.apache.skywalking.oap.server.receiver.register.provider.handler.v6.grpc.ServiceInstancePingServiceHandler
 - 68 [grpc-default-executor-114] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 295, will send a reset command 
to agent side

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to