search

DOI-USGS / dataRetrieval

This R package is designed to obtain USGS or EPA water quality sample data, streamflow data, and metadata directly from web services.
https://doi-usgs.github.io/dataRetrieval/
Other
256 stars 85 forks source link

All requests timing out? #622

Closed mspear2 closed 1 year ago

mspear2 commented 2 years ago

It seems all readNWISdv() requests, even basic ones, are timing out. I had momentary success with the following code, but it seems to only successfully retrieve data one out of every 10 times, timing out in the other attempts.

readNWISdv(siteNumbers = "05533600", parameterCd="00060", startDate = as.Date('2019-06-01'), endDate = as.Date('2019-06-30'))

ldecicco-USGS commented 2 years ago

I'm trying to get some details from the NWIS folks! Looks like the "uv" service is still working but pretty much everything else is timing out.

WQP is fine.

mspear2 commented 2 years ago

I appreciate the quick reply. I'll stay tuned.

From: Laura DeCicco @.> Sent: Thursday, June 16, 2022 12:04 PM To: USGS-R/dataRetrieval @.> Cc: Michael J Spear @.>; State change @.> Subject: Re: [USGS-R/dataRetrieval] All requests timing out? (Issue #622)

I'm trying to get some details from the NWIS folks! Looks like the "uv" service is still working but pretty much everything else is timing out.

WQP is fine.

— Reply to this email directly, view it on GitHubhttps://github.com/USGS-R/dataRetrieval/issues/622#issuecomment-1157921720, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGBIKY55226SGWUMF3MDXHLVPNNCTANCNFSM5Y7N5PAA. You are receiving this because you modified the open/close state.Message ID: @.***>

ldecicco-USGS commented 2 years ago

The initial guess is someone's doing a massive parallel processing job and hitting the services like crazy. The server logs right now are off the charts. The dev-ops team is on the case, I'll let you know when I hear anything.

ldecicco-USGS commented 2 years ago

Things seem back to normal! Let me know if you are still running into any timeouts.

joshualerickson commented 2 years ago

Hey @ldecicco-USGS, in response to hitting the servers too frequently, is there a rate limit that dev-ops would like to see for the service, e.g 30/min, 60/min, etc? Working with the whitewater package to try and not overload requests and one solution by @HenrikBengtsson was to put a rate limit on the requests, see discussion here. This would allow the user to still use parallel (future framework) while respecting the server. Thoughts?

dblodgett-usgs commented 2 years ago

@jkreft-usgs might want to weigh in here?

ldecicco-USGS commented 1 year ago

Sorry for the super delayed response. I never heard back from the developers specifically. I would say at this point, pick a number like 30/min. If we ever find we need to change it, I can submit an Issue to the whitewater package.