One point of clarification...
I understand the queue problem where I should have it larger. Right now,
that's not going to happen.
Duplicates are one problem...but *bandwidth* is equally as important to
me. I can increase my queue size, but I'm using up massive more chunks of
University bandwidth unnecessarily. I don't think that will come back to
haunt me at all, but it could with other sites. And I know of one where it
will.
My level 2 ingest and storing/serving data server has a 1 TB hard drive,
and it's 75% full this morning. A bit uncomfortably high for me right now,
but I can live with it. But I still have to reject products with a larger
queue, and that bandwidth issue is still there. So my argument is that the
solution, ultimately, lies not in increasing the queue, but why are we
seeing a sudden duplicate feed from one NWS region and how can it be
fixed? God forbid it happen on all regions. I'm trying to help UNIDATA nip
this in the bud so that it doesn't happen and people come into work on
Monday to find out that since Friday night, there server has been down
with a 100% full hard drive...
*******************************************************************************
Gilbert Sebenste ********
(My opinions only!) ******
Staff Meteorologist, Northern Illinois University ****
E-mail: sebenste@xxxxxxxxxxxxxxxxxxxxx ***
web: http://weather.admin.niu.edu **
*******************************************************************************
