Skip to content
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

Truncated netcdf data downloads #8

Open
ffang10 opened this issue Feb 26, 2020 · 0 comments
Open

Truncated netcdf data downloads #8

ffang10 opened this issue Feb 26, 2020 · 0 comments

Comments

@ffang10
Copy link

ffang10 commented Feb 26, 2020

Our user reported incomplete data download cases from this server

https://goldsmr5.gesdisc.eosdis.nasa.gov/opendap/

All cases appear to use the fileout netcdf handler for the .nc4 responses with subsetting, and mostly for the M2I3* datasets under 'MERRA2', which are very large granules themselves. A typical URL is:

https://goldsmr5.gesdisc.eosdis.nasa.gov/opendap/MERRA2/M2I3NPASM.5.12.4/2017/03/MERRA2_400.inst3_3d_asm_Np.20170324.nc4.nc4?T[0:7][0:41][0:360][0:575],H[0:7][0:41][0:360][0:575],O3[0:7][0:41][0:360][0:575],QV[0:7][0:41][0:360][0:575],PHIS[0:7][0:360][0:575],PS[0:7][0:360][0:575],lat[0:360],time[0:7],lon[0:575],lev

While these are large data requests that can overwhelm the server sometimes (presumably when the download incompleteness occur?), a data download would either be a success or failure (It appears that the httpd has status 200 in the access logs).

Caching in the server was turned on. I wonder if cache management in server can interfere with a download, given the pattern of the failures which were occasional and quasi-periodical.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant