Hi, Currently if MB node got killed unexpectedly non-durable topic subscriptions bind to that node will remain in cluster. This can cause unexpected behaviors in cluster since that node has already removed.
IMO these topic subscriptions can clean up in two methods. 1. During each MB node start up, remove all non-durable topic subscriptions for it's local node id. (This will ensure newly started node won't receive any non-durable topic messages related to previously killed MB node with same node id) 2. Cluster coordinator should remove all non-durable topic subscriptions when a member left from cluster. (This can be a problem if coordinator node killed. If there's a method to get previous coordinator node id by newly elected coordinator this method can be implemented) How should we do the clean up. WDYT? Regards, Pumudu -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
