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

[NOAAPORT #MJB-944803]: rhel8 noaaport gaps

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: [NOAAPORT #MJB-944803]: rhel8 noaaport gaps
  • Date: Tue, 01 Nov 2022 12:44:33 -0600
Sean,

Yes, and I went back through my RedHat ticket notes on that, and found how
> they initially determined that we were exceeding the default udp read
> buffer
> ss -numa
> The skmem field d# value is the dropped packets before they are
> de-multiplexed into the socket. We're steady at 0 dropped packets. Back
> before we implemented that -R argument, we were seeing that # increase over
> time as data was getting dropped.
> It doesn't sound like you guys have found anything RHEL8 specific, I've got
> a ticket open with RedHat now, hopefully they can spot something, I'll let
> you know.
>

If the O/S isn't dropping packets and the noaaportIngester(1) receive
buffer is large, then the only way you could see gaps is if the packets are
arriving faster than noaaportIngester(1) can process them.

Is the VM doing anything else?

--Steve



Ticket Details
===================
Ticket ID: MJB-944803
Department: Support NOAAPORT
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.