Firebase存储和云功能-ECONNRESET [英] Firebase Storage & Cloud Functions - ECONNRESET

问题描述

我开发了Firebase Cloud功能，该功能可以处理对上传图像的几种操作. 我的代码基于本文档文章和 Google云存储软件包.

I developed a Firebase Cloud function that processes several manipulations on uploaded images. My code is based on this documentation article and this Cloud Function example. Hence, it is using Google Cloud Storage package.

几乎所有时间都能正常运行，但是有时在上传到存储或从存储中删除时出现此错误:

It is working fine almost all the time, but sometimes I am getting this error when uploading to or deleting from Storage :

 Error: read ECONNRESET
    at exports._errnoException (util.js:1026:11)
    at TLSWrap.onread (net.js:569:26)

我正在使用应用程序的默认存储桶，该存储桶由event.data.bucket引用.

I am using the default bucket of my application, referenced by event.data.bucket.

即使我的代码与我之前链接的Function示例非常接近，也让我知道您是否需要其他信息或代码段.

Let me know if you need additional information or code snippets, even if my code is really close to the Function example I linked before.

我发现了此GitHub问题，但我检查了自己是否正在返回每次都有诺言.例如，这是触发错误的删除部分:

I found this GitHub issue, but I checked that I am returning a promise everytime. For example, here is the deletion part that triggers the error :

index.js

exports.exampleFunction = functions.storage.object().onChange(event => {
    return f_thumbnails.exampleFunction(event);
});

example_function.js

module.exports = exports = function (_admin, _config) {
    admin = _admin;
    config = _config;

    return {
        "exampleFunction": function (event) {
            return exampleFunction(event);
        }
    };
};

const exampleFunction = function (event) {
    const gcsSourceFilePath = event.data.name;
    const gcsSourceFilePathSplit = gcsSourceFilePath.split('/');
    const gcsBaseFolder = gcsSourceFilePathSplit.length > 0 ? gcsSourceFilePathSplit[0] : '';
    const gcsSourceFileName = gcsSourceFilePathSplit.pop();
    const gceSourceFileDir = gcsSourceFilePathSplit.join('/') + (gcsSourceFilePathSplit.length > 0 ? '/' : '');

    // Not an image
    if (!event.data.contentType.startsWith('image/')) {
        console.log('Not an image !');
        return;
    }

    // Thumbnail
    if (gcsSourceFileName.startsWith(config.IMAGES_THUMBNAIL_PREFIX)) {
        console.log('Thumbnail !');
        return;
    }

    const bucket = gcs.bucket(event.data.bucket);
    const gcsThumbnailFilePath = gceSourceFileDir + config.IMAGES_THUMBNAIL_PREFIX + gcsSourceFileName;


    // File deletion
    if (event.data.resourceState === 'not_exists') {
        console.log('Thumbnail deletion : ' + gcsThumbnailFilePath);
        return bucket.file(gcsThumbnailFilePath).delete().then(() => {
            console.log('Deleted thumbnail ' + gcsThumbnailFilePath);
        });
    }
    ...

推荐答案

这似乎与google-cloud-node库的套接字处理以及Cloud Functions环境中的默认套接字超时有关.

This seems to be related to the google-cloud-node library's handling of sockets, and the default socket timeout in the Cloud Functions environment.

用户验证的一种解决方案是修改库调用requests的方式，而不是通过指定forever: false来使套接字永远保持打开状态，例如

One solution verified by a user is to modify the way the library invokes requests, to not keep the socket open forever by specifying forever: false, eg.

var request = require('request').defaults({
  timeout: 60000,
  gzip: true,
  forever: false,
  pool: {
    maxSockets: Infinity
  }
});

这是硬编码在 相关公开问题，以获取有关该问题的更多详细信息以及带有已应用补丁.

This is hardcoded in packages/common/src/utils.js, so you'll need to vendor a copy of the modified library into your project rather than include it as an NPM dependency. See the related public issue for more details on the issue and a link to a fork with the patch applied.

这篇关于Firebase存储和云功能-ECONNRESET的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！