Thursday, 15 April 2010

meteor - How to handle CollectionFS saving failures -


I am using the collection fs and especially the S3 storage adapter.

Most of the files are fully uploaded and I can download them later with no problem.

Sometimes I get a file that looks right ( files.insert (blob, callback) returned to the callback with no errors) but later when I sent them < I'm going to download the code> fsFile.url () return null .

Says:

If a storage adapter fails to save any copies in the designated store, then the server will try again to save them from time to time. After a configurable number of unsuccessful attempts to save, the server will lose.

But there is no such callback that I know about such failure. Also, when I look at fsFile.uploadProgress () I get 100%.

The basic problem of this type is that everything looks fine during upload and my app only detects a problem,

  • What else

    1. FsFile.url () return null symbol?

    Here one of these is broken mongodb in fsFile items:

      {"_id": " UqayajqCv68HmEJhu "," original ": {" updatedAt ": ISODate (" 2015-03-16T23: 04: 37.200Z ")," size ": 699072," type ":" "}," piece size ": 20 9 7152 , "Chunkcount": 0, "chunk sum": 1,}  
  • server side, 3 events were stored on the archived , uploaded and error .

      images.on ('Error', function (file obj) {console.log ("" file + + + + + + "with" + OBJE file. Get the error ")});  

    There is no documentation about it, since the rikes and aldead clears the README.


    No comments:

    Post a Comment