Hi Siro, IMO, since we already have a periodic task to catch the messages that are expired, that should be sufficient in terms of clearing expired messages from the database.
So batching messages that expire during the delivery path for a different deletion task is redundant. WDYT ? (Merely skipping such messages with the assumption that periodic worker will process them should be enough.) On Mon, Sep 5, 2016 at 11:28 AM, Sajini De Silva <saj...@wso2.com> wrote: > Its hard to say what should be the exact correct time interval. IIt > depends on the messaging rate actually. I think one DB call per 10 seconds > seems oky. Are there any issues with this value? > > > On Mon, Sep 5, 2016 at 11:16 AM, Sirojan Tharmakulasingam < > siro...@wso2.com> wrote: > >> Hi all, >> >> At the MB message delivery path, we capture the expired messages and >> batch it for a batch delete from the database rather than issue a delete DB >> call for each expired messages. >> >> what is the suitable time interval for batching the expired messages for >> the DB batch delete? >> >> The current suggestion is 10sec. Your suggestions please... >> >> Regards, >> -- >> Sirojan Tharmakulasingam >> Software Engineer, WSO2 Inc. http://wso2.com >> Email: siro...@wso2.com >> Mobile: +94779797913 >> > > > > -- > Sajini De SIlva > Senior Software Engineer; WSO2 Inc.; http://wso2.com , > Email: saj...@wso2.com > Blog: http://sajinid.blogspot.com/ > Git hub profile: https://github.com/sajinidesilva > > Phone: +94 712797729 > > -- Cheers, Hasitha Amal De Silva Senior Software Engineer Mobile : +94772037426 Blog : http://devnutshell.tumblr.com/ WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
