Re: [keycloak-user] deletion execution schedule EVENT_ENTITY

I suppose in this case the problem is that query to identify records to delete takes a long time, but number of actual records to delete is small. In that case it makes sense to prolong the 'garbage collection' period. If the number of records to delete is big, and that causes a long table lock then the situation with bigger timeout may make things even worse. Did you maybe check what indexes are set on this table if any? Depending on the database, creating a different index or changing an index type can make a huge difference. Another way to maybe address this would be to only delete small number of records at a time: delete from EVENT_ENTITY where EVENT_ID in (select EVENT_ID from EVENT_ENTITY where REALM_ID=:1 and EVENT_TIME<:2 limit 100) On Wed, Sep 30, 2015 at 2:33 PM, Hipfinger Martin (BCC.ÖBB.TicketShop.MA <http://bcc.xn--bb-eka.ticketshop.ma>) <Martin.Hipfinger(a)oebb.at&gt; wrote: