Difference: ReleaseNotes1841 (20 vs. 21)

Revision 212008-09-09 - AlessioGianelle

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

Release notes for Patch #1841

Line: 41 to 41
 
  • Known issues:
    • Very often, especially under high loads, the virtual memory occupation for the glite-wms-workload_manager process may reach very high values, such as one Gigabyte and more. This is not about a memory leak, but simply the effect of a well-known problem with the allocator which comes with the glibc (the so called ptmalloc2). See tcmalloc for a more detailed explanation. This problem can be avoided using run-time redirection to whatever lock-free, optimized alternative allocator, to avoid excessive swap activity. It is highly suggested doing so wherever RAM is less than or equal to 4Gb. Here is our recipe which makes use of the TCmalloc, such an alternate allocator distributed by Google under BSD license:
      • install the two rpms, google-perftools-devel-???.rpm and google-perftools-???.rpm (just pick up the latest version, older versions should work anyway, just in case),
Changed:
<
<
      • enable the malloc redirection for the WM by editing the glite-wms-wm script. It is just a matter of removing the comment in the following line:
>
>
      • enable the malloc redirection for the WM by editing the glite-wms-wm script. It is just a matter of removing the comment in the following line:
 #use_google_perf_tools=1
Deleted:
<
<
 
    • Bug #39641: User proxy mixup for job submissions too close in time
    • Bug #40951: Cleared event is not logged for nodes
    • Bug #40982: When a collection is aborted the "Abort" event should be logged for the sub-nodes as well /2
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback