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

[IDV #JTW-108801]: IDV opens too many connections on NCAR RDA

> Hi Yuan,
> 
> Thanks for taking a look. I took a look at the Data Reading thread count, 
> which was set to 4, so that's fine. I will let you know if I have any other 
> problems.
> 
> Marty

No problem, try the aggregation best time series again, I didn't see any issue 
loading and creating a display in both 5.6 and 5.7 version. Otherwise, 
client-side aggregate might create too many connections.

Yuan
> _____________________________
> Marty Baxter, Ph.D.
> Professor of Meteorology
> Department of Earth and Atmospheric Sciences
> Central Michigan University
> (989) 774-2055
> ________________________________
> From: Unidata IDV Support <address@hidden>
> Sent: Tuesday, March 3, 2020 12:58 PM
> To: Baxter, Martin A <address@hidden>
> Cc: address@hidden <address@hidden>
> Subject: [IDV #JTW-108801]: IDV opens too many connections on NCAR RDA
> 
> > Full Name: Marty Baxter
> > Email Address: address@hidden
> > Organization: Central Michigan University
> > Package Version: 5.6
> > Operating System: Mac
> > Hardware:
> > Description of problem: Hi Yuan,
> >
> > I connected to the RDA THREDDS server using through the IDV catalog, as I 
> > would any TDS. It is password protected. I think I was here: 
> > https://rda.ucar.edu/thredds/catalog/catalog_ds083.3.html. I first tried 
> > the data in the "aggregation" folder and I received an error from IDV. Then 
> > I tried the "files" folder and it worked. I loaded in the data and made 
> > some plots. Later my login on the RDA was suspended.  They said this was 
> > because, "You were blocked because you opened so many connections to our 
> > server that you blocked other users from connecting. It looks like you 
> > might have been using IDV. You need to manage the number of connections you 
> > make to our server. We allow any single user to have a maximum of 10 
> > concurrent connections. We have unblocked your account, but if this problem 
> > happens again, you will be blocked permanently." I asked them how many 
> > connections I had made and they said, "We don't know the exact number but 
> > it was well over 100. IDV/THREDDS was using all
  o
> f the available processes up to our maximum available of 256."
> >
> > I was not aware that I was opening so many connections. Something is wrong 
> > here - the user shouldn't be able to do this, at least without knowing they 
> > are opening so many connections. Is this behavior that you are aware of? 
> > Thanks for your help. I am afraid to try to reproduce the error because I 
> > don't want to be permanently kicked off of the RDA!
> >
> >
> Hi Marty,
> 
> I tried the same catalog, both files and aggregation folder works for me. I 
> loaded more than 300-time steps a couple of times, not getting any trouble .
> In the IDV User Preferences > System tab, there is a setting of"Data Reading" 
> thread count, you can double-check to make sure it is a reasonable number 
> there.
> I ran IDV 5.7, there is a bug in the time matching in 5.6 version. But if you 
> are not doing any time matching, this should not be an issue.
> 
> Well, I don't know what to suggest, I will keep monitoring if I get the 
> blocked.
> 
> Yuan
> 
> Ticket Details
> ===================
> Ticket ID: JTW-108801
> Department: Support IDV
> 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.
> 
> 
> 
> 


Ticket Details
===================
Ticket ID: JTW-108801
Department: Support IDV
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.