zhaoxunyong commented on issue #3448: Clients of Skywalking cannot be register by themselves. URL: https://github.com/apache/skywalking/issues/3448#issuecomment-530202893 But half a day is gone by, I still couldnāt see some of agent re-registerd by themselves, according to you, it will re-registered in 10 minuties. It's so weird, and just this logs showing up: ------ 2019-09-11 08:20:59,044 - org.apache.skywalking.oap.server.core.register.service.ServiceInstanceInventoryRegister - 108 [grpc-default-executor-529] WARN [] - Service instance 174 heartbeat, but not found in storage. 2019-09-11 08:20:59,045 - org.apache.skywalking.oap.server.receiver.register.provider.handler.v6.grpc.ServiceInstancePingServiceHandler - 68 [grpc-default-executor-529] WARN [] - Can't find service by service instance id from cache, service instance id is: 174, will send a reset command to agent side 2019-09-11 08:20:59,514 - org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher - 51 [grpc-default-executor-530] WARN [] - Can't find service by service instance id from cache, service instance id is: 177 2019-09-11 08:20:59,556 - org.apache.skywalking.oap.server.core.register.service.ServiceInstanceInventoryRegister - 108 [grpc-default-executor-530] WARN [] - Service instance 177 heartbeat, but not found in storage. 2019-09-11 08:20:59,557 - org.apache.skywalking.oap.server.receiver.register.provider.handler.v6.grpc.ServiceInstancePingServiceHandler - 68 [grpc-default-executor-530] WARN [] - Can't find service by service instance id from cache, service instance id is: 177, will send a reset command to agent side 2019-09-11 08:21:00,004 - org.apache.skywalking.oap.server.receiver.trace.provider.parser.SegmentParseV2 - 98 [grpc-default-executor-530] WARN [] - Cannot recognize service instance id [174] from cache, segment will be ignored Please help me again, because I don't wanna reboot my production agent, thanks.
---------------------------------------------------------------- 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