[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AWIPS #PKL-603844]: AWIPS2 Sever Overload

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [AWIPS #PKL-603844]: AWIPS2 Sever Overload
  • Date: Fri, 22 Jul 2016 10:00:13 -0600
> Good morning Michael,
> 
> Thanks for having a look at this.
> 
> It is very odd there are so many of the old files. It appears you left them
> intact? Should the me removed?
> 
> I logged in this morning and there are currently 43 of the repack processes
> running an the load average is still absurdly high: ~54 . I also looked at
> all of the h5repack processes all but three of those processes appear to be
> processing this file:
> 
> awips    26506 14.4  0.0  24568  9680 ?        R    08:56  14:08 h5repack
> -f LZF /awips2/edex/data/hdf5/goessounding/go
> essounding-2016-06-02-10.h5
> /awips2/edex/data/hdf5/goessounding/goessounding-2016-06-02-10.h5.repacked
> 
> I/m wondering if it  is it OK to delete that file?
> 
> While I was composing this message the thee process not processing the
> above file finished. So the only h5repack processes are for the above file.

Yep, these can and should be removed, any HDF5 files older than a week (or so) 
can be deleted, especially the very old files which were somehow missed by data 
purging. 





Ticket Details
===================
Ticket ID: PKL-603844
Department: Support AWIPS
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.