Difference: DpmFlushOldRequests (2 vs. 3)

Revision 32007-10-16 - LanaAbadie

Line: 1 to 1
 
META TOPICPARENT name="DataManagementDocumentation"

DPM Flushing Old Requests utility

Line: 30 to 30
 Then look at the log file produced dpm-flush-oldreq.log to see if the execution was successful.

Remark

Changed:
<
<
if the number of requests to e flushed is very big around millions of row, it might be a good idea to start this script before migrating to a new DPM version so that it doesn't impact the performance of the DPM.
>
>
if the number of requests to be flushed is very big around millions of row, it might be a good idea to start this script before migrating to a new DPM version so that it doesn't impact the performance of the DPM. it takes roughly one hour to delete around a few millions of old requests. Of course the execution time will depend on the DPM load.
 

Any problems or questions?

  • if you get the following error in the log file: the total number of locks exceeds the lock table size, then you need to increase the innodb_buffer_size as follows:
Line: 40 to 40
 send me a mail

-- LanaAbadie - 15 Oct 2007

Added:
>
>
META FILEATTACHMENT attachment="dpm-flush.tar" attr="" comment="" date="1192565006" name="dpm-flush.tar" path="dpm-flush.tar" size="235520" stream="dpm-flush.tar" user="Main.LanaAbadie" version="1"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback