Session Storage Reduction in Size
I currently have a customer who has a session storage size of 975G.
They have determined they only need 850G to store 7-8- days of data. The 975G is currently being utilized.
If they simply going to session storage and change the value from 975-850G.
Q1 When or at What point will the space be reclaimed (125G)
Q2 Will this cause a major impact on the server or cuase an issue with current session data being written out?
Thanks
I haven't done this exercise recently (maybe dT 5.0? or was it 4.2?) but setting the limit lower should "just work". The dT server will age out the old stuff as soon as you drop the limit. You shouldn't see any perf impact on the session writing.
Just to add to what Rob said.
Our Continuous Session storage mechanism always writes chunks of 5GB files to the cont session directory. If we reach the quota (or if less than 1GB of free disk space is available) the oldest 5GB chunk is deleted. This all happens "on the fly". So - if you change your quota dynaTrace will start removing the oldest 5GB files
Andi
Andi,
The logic to remove the oldest 5GB files has a problem when we deal with profiles with varying data load. This may have to be changed to oldest modified 5GB files. here is the RFE for the same RFE: change the logic to remove session files
-Sreerag
I did inform the customer that the decision to reduce the session storage would in fact remove session data in a non-discriminatory manor and that there is no balance or weighting in removal of session data over his application profiles. The server will simply age out of the oldest session data.
I do like the RFE to allow some control over session removal
