You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When the jraft server started, NacosStateMachine will load the jraft snapshot after initialization. If it is persistent data, PersistentClientOperationServiceImpl will start working, and the readSnapshot method will be called.
IpPortBasedClient is initialized one by one, publishes the ClientRegisterServiceEvent event to the downstream, and then adds the client to the clientManager.
After ClientServiceIndexesManager processes this event and builds the index, it will publish the ServiceChangedEvent event, which will then be processed by NamingSubscriberServiceV2Impl and submit the PushDelayTask delay task. When this task is executed, generatePushData will be called, which will have the logic to obtain the client from the clientManager.
There is a problem here. Since the event is processed asynchronously, there may be a situation where the corresponding client cannot be found and needs to be fixed.
Expected behavior
When the jraft snapshot data is loaded, the cache data of ClientServiceIndexesManager should be consistent with the cache data of ClientServiceIndexesManager in ServiceStorage.
Actually behavior
A clear and concise description of what you actually to happen.
The text was updated successfully, but these errors were encountered:
Describe the bug
When the jraft server started, NacosStateMachine will load the jraft snapshot after initialization. If it is persistent data, PersistentClientOperationServiceImpl will start working, and the readSnapshot method will be called.
IpPortBasedClient is initialized one by one, publishes the ClientRegisterServiceEvent event to the downstream, and then adds the client to the clientManager.
After ClientServiceIndexesManager processes this event and builds the index, it will publish the ServiceChangedEvent event, which will then be processed by NamingSubscriberServiceV2Impl and submit the PushDelayTask delay task. When this task is executed, generatePushData will be called, which will have the logic to obtain the client from the clientManager.
There is a problem here. Since the event is processed asynchronously, there may be a situation where the corresponding client cannot be found and needs to be fixed.
Expected behavior
When the jraft snapshot data is loaded, the cache data of ClientServiceIndexesManager should be consistent with the cache data of ClientServiceIndexesManager in ServiceStorage.
Actually behavior
A clear and concise description of what you actually to happen.
The text was updated successfully, but these errors were encountered: