-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP error when calling LLC4320 outputs #269
Comments
The same syntax was working fine till last week so I'm not sure what's changed... |
The ECCO data portal is down unfortunately. Completely beyond our control. |
Or maybe this error is not related to this. Pinging @martindurant for possible fsspec API change? Martin, does this error make sense to you?
|
This would indicate that the size of the file was not available, which maybe the server doesn't support it (unlikely if it worked before). More likely, there either is no size temporarily, or the server is doing some kind of forwarding. It is worth running debug on the exception above, to see if the response looks like data or like some error message. If you can reach the same URL using requests and can fetch specific bytes ranges with the Range header, but fsspec keeps falling back to streaming, then indeed there may be a bug in fsspec. |
As of right now, https://data.nas.nasa.gov/ecco/data.php?dir=/eccodata/llc_4320/compressed/0000154224 Correction the "size" column in the html website is apparently independent of the HTTP headers. |
I passed this on to the ECCO portal maintainer and he said that the "size"s are not shown regularly on the website. He asked whether I could download some data from the links upon which I could, so he says that the portal should be working fine... |
@martindurant And I apologize and advance for my ignorance but could you show me the syntax for debugging? I'm a beginner in fsspec... |
I meant literally typing |
Oh, I see this is within dask. You might want to run without dask, just as far as the exception. I have no idea how to do that with |
The following works with fsspec 0.8.5 and 2021.6.0 import fsspec
url = "https://data.nas.nasa.gov/ecco/download_data.php?file=/eccodata/llc_4320/compressed/0000154224/Eta.0000154224.data.shrunk"
with fsspec.open(url, mode='rb') as fp:
# test size works
assert fp.size == 562551864
with fsspec.open(url, mode='rb') as fp:
# test seek works
fp.seek(2) @roxyboy could you try the same code from your environment? |
Also, @roxyboy's example failed to reproduce for me on https://us-central1-b.gcp.pangeo.io/. Following code works fine. from xmitgcm import llcreader
model = llcreader.ECCOPortalLLC2160Model()
dsw = model.get_dataset(varnames=['Eta'], type='latlon').sel(time=slice('2012-02-01','2012-04-30'),
i=slice(7600,None),i_g=slice(7600,None),
j=slice(4600,5300),j_g=slice(4600,5300),
k=0)
dsw.Eta.isel(time=0).plot() |
It seems to working again for me too... I'll close this, sorry for the disturbance. |
Our CI also picked up the same exact error a few days ago: https://github.com/MITgcm/xmitgcm/runs/2657251546?check_suite_focus=true#step:6:87 To me, this indicates an intermittent error on the ECCO data portal. It would be great to get some confirmation from the NASA engineers whether this could be the case. |
Changing the domain seems to give the error again:
Does this have to do with this new patch of data being saved as another file? |
No, I think that the llc2160 files are indeed inaccessible right now. It has changed multiple times just over the past few hours. https://data.nas.nasa.gov/ecco/data.php?dir=/eccodata/llc_2160/compressed/0000092160 "Due to high demand our filesystem has become unresponsive." |
And now it's back. |
It seems that the connection to the ECCO portal is intermittent again. I'm getting the HTTP error again and when trying the snippet above, I got an assertion error the first try but it ran on second attempt. |
Dear xmitgcm community,
I started getting the following error when trying to call the LLC4320 run from the NASA ECCO portal using the
llcreader
:Checking with the NASA Ames Research Center, it seems that their portal is up and running. I haven't able to track down the cause for this error but could you please advise what I should try?
Thank you.
The text was updated successfully, but these errors were encountered: