Hi All,
Is there any reason for running the session clean up task and operation
data clean up task separately? Since they are performing a combination of
select and delete operations on the same table, there is a chance that they
end up in a dead-lock if they happen to run concurrently. So shall w
Hi Ruwan,
On Mon, Apr 24, 2017 at 2:32 PM, Ruwan Abeykoon wrote:
> Hi Dinali,
> Do we know any figures for
> >> time taken by "deleteSTOREOperationsTask" operation
>
> We need to measure how long it takes to complete the data deletion per X
> number of records. Only then we could arrive at a co
On Mon, Apr 24, 2017 at 3:40 PM, Thanuja Jayasinghe
wrote:
> Hi Ruwan,
>
> On Mon, Apr 24, 2017 at 2:32 PM, Ruwan Abeykoon wrote:
>
>> Hi Dinali,
>> Do we know any figures for
>> >> time taken by "deleteSTOREOperationsTask" operation
>>
>> We need to measure how long it takes to complete the da
Hi Dinali,
Do we know any figures for
>> time taken by "deleteSTOREOperationsTask" operation
We need to measure how long it takes to complete the data deletion per X
number of records. Only then we could arrive at a correct strategy.
Having stored-procedure or handling it on queries does not make
Hi Dinali,
+1 for the 2nd solution.
Since this operation takes a considerable amount of time, it's better to
handle this from the DB side during the off-peak hours.
Thanks,
Thanuja
On Fri, Apr 21, 2017 at 11:12 AM, Dinali Dabarera wrote:
> Hi All,
>
> There is a public issue reported in [3],
Hi All,
There is a public issue reported in [3], due to a deadlock happened in the
long-running scenario.
This deadlock occurs due the time taken by "deleteSTOREOperationsTask"
operation which is responsible for cleaning session data which is scheduled
daily.
We have currently come up with two
