跳转到主内容

使用内部服务器500时、StorageGRID S3上传间歇性失败

Views:
4
Visibility:
Public
Votes:
0
Category:
storagegrid<a>2009455523</a>
Specialty:
sgrid
Last Updated:

适用场景

  • StorageGRID 11.5
  • FileNet应用程序

问题描述

对某些对象的网格执行FileNet Application S3操作失败:
 
2023-02-02 02:48:00,259  com.<xxxx> ERROR - DMS11132I: <xxxx> Document Import robot failed to commit batch:<xxxx>
2023-02-02 02:48:00,264 <xxxx> ERROR - <xxxx>: FNRCC0243E: CONTENT_ASA_NOT_ENOUGH_REPLICAS_WRITTEN: Not enough replicas were written to satisfy the synchronous upload requirement, written 0, required 1. Area Id: [{<xxxx>}]; Device Id: [{<xxxx>}]; Content Id: [{<xxxx>}]; HashSeq: [<xxxx>]; Successful replicas: []; Failed replicas: [{<xxxx>} : <xxxx>: FNRCC0317E: CONTENT_S3_OPERATION_FAILED: S3 storage device [CreateContent] call failed for Object: <xxxx>] errorStack={at <xxxx>(Redirector.java:392)
 
StorageGRID bycast-err.log报告:
 
Jan 30 08:06:57 <xxxx> ADE: |12468221 0472863229 S3RQ POPD 2023-01-30T08:06:57.108038| ERROR   1880 <xxxx> S3RQ: S3 request error: connection=<xxxx>, Resource=<xxxx>, HTTP Status Code=500, ErrorMsg=InternalError, ErrorType=Client CustomErrorMessage={<none>}, Details={asyncPop error: no producer}
 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.