Hi Sirojan, Yes, In user's perspective it is better not to show the expired messages.
How are we going to filter out the expired messages from UI? Since we have the expiry time information in the database, I think we can use that information to filter. On Tue, Oct 4, 2016 at 12:00 PM, Sirojan Tharmakulasingam <[email protected]> wrote: > Hi All, > > Currently, we have two tasks to deal with expired messages. > > 1. Pre-delivery expiry message deletion task --> Will catch the expired > messages at the Message flusher > 2. Periodic message deletion task --> each 15 minutes it checks expired > messages and deleted them for the messages which are not in our safety slot > count region (we have this buffer assuming that those will be assigned to > slot delivery worker in the near future) > > The problem: > > Even though the messages are expired, they are still residing in the > database for some time. > > 1. Messages that are not in the safe-zone - 15 minutes (worst case) - > until the periodic task runs > 2. Messages that are in the safe-zone - until a subscription comes and > messages tries to deliver and get caught at the flusher/ > > During the above time, those messages are in the DB even though they are > expired. In the UI we are showing them as valid messages and valid message > count during the aforementioned time. > > Solution: > > 1. We are not showing the messages in the UI even though they are in the > DB (waiting for delete by the expiry tasks) > > WDYT? Suggestions, please? > > Regards, > -- > Sirojan Tharmakulasingam > Software Engineer, WSO2 Inc. http://wso2.com > Email: [email protected] > Mobile: +94779797913 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Asanka Abeyweera Senior Software Engineer WSO2 Inc. Phone: +94 712228648 Blog: a5anka.github.io <https://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
