KERs currently do not correctly respond to remote KERs that disappear without notification; i.e. the KD lease is not renewed in time and so other KERs are notified that a KER is now gone (i.e. Removing peer that is now gone: http://localhost:8081).
This is caused by the fact that no further action is taken to also remove the smart connectors associated with this remote KER and because this does not happen, they are still taken into account when relevant KIs are activated. This problem only occurs when the remote KER is killed without being able to send a stop message to other KERs.
So, fix this by notifying all the SCs in this KER to update their OtherKnowledgeBaseStore accordingly.
KERs currently do not correctly respond to remote KERs that disappear without notification; i.e. the KD lease is not renewed in time and so other KERs are notified that a KER is now gone (i.e.
Removing peer that is now gone: http://localhost:8081).This is caused by the fact that no further action is taken to also remove the smart connectors associated with this remote KER and because this does not happen, they are still taken into account when relevant KIs are activated. This problem only occurs when the remote KER is killed without being able to send a
stopmessage to other KERs.So, fix this by notifying all the SCs in this KER to update their OtherKnowledgeBaseStore accordingly.