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.
Tom, Would you please tell us where the LDM product-queue is on Colaweb? Is it on a disk that is local to Colaweb or is it on a disk that is remote from Colaweb and, consequently, accessed via a network protocol (e.g., NFS)? I ask because this information will likely be useful for the next person who has this problem. > As expected the bare metal cola6 performed just fine with the same config > that was failing on colaweb. > > So I took another look at the NFS options for where the LDM was trying to > write, and switched from async to sync. For the last 3 hours we have > received data at the expected rate. This is the first time we have > encountered an app that overloaded NFS async so much. I plan to do more > testing with how NFS and ZFS are handling sync'ing, but for now it’s finally > grabbing data. > > At this point I think you guys can close the case. And we thank you for all > your help! Regards, Steve Emmerson Ticket Details =================== Ticket ID: MIY-170840 Department: Support LDM Priority: Normal Status: Closed =================== 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.