Download size cannot be zero bytes

15535
Reporter: mdoering
Assignee: mdoering
Type: Bug
Summary: Download size cannot be zero bytes
Priority: Minor
Resolution: WontFix
Status: Resolved
Created: 2014-04-15 18:33:41.766
Updated: 2014-04-16 12:16:45.205
Resolved: 2014-04-16 12:16:45.183
        
    

Attachment Screen Shot 2014-04-15 at 18.32.59.png

Author: mdoering@gbif.org
Comment: The webservice returns zero bytes, but it only happens on dev not in the production portal. You can also  download the archive fine on dev
Created: 2014-04-16 11:20:05.772
Updated: 2014-04-16 11:20:42.716

Author: mdoering@gbif.org
Created: 2014-04-16 11:33:05.47
Updated: 2014-04-16 11:33:05.47
        
There are 2565 downloads in our prod registry that have status succeeded, but size=0 bytes.
Some of them are from aimee like this one:
 http://api.gbif.org/v0.9/occurrence/download/request/0001571-140402090945128.zip

Other are not:
 http://api.gbif.org/v0.9/occurrence/download/request/0001059-140404111544719.zip

    

Author: mdoering@gbif.org
Created: 2014-04-16 12:16:31.687
Updated: 2014-04-16 12:16:31.687
        
The download code in general is fine. But if a download file cannot be accessed while oozie triggers the download callback service (e.g. cause we badly mounted the filesystem or some download errors happened) the filesize of zero bytes sticks forever, even if the mount is later added correctly.

I'd suggest to ignore this bug as it seems to have very low priority to update the older downloads and correct file sizes. If that wanted we should create a small script that iterates over all downloads and updates the size based on the current file size.