0

使用Opscenter的备份服务失败,出现AWS S3错误 - 500 InternalError。对于具有此错误代码的不同文件,它在3-4个节点上失败。 AWS S3文档建议重试该操作(我们遇到内部错误,请重试)。我只能在代理日志和S3日志中看到此文件名和错误一次,这意味着在此错误发生后没有重试。有没有办法在opscenter中启用S3 500错误代码(InternalError)的重试?有关如何解决此错误的任何建议?Opscenter备份失败 - S3 500 InternalError

Error while sending [email protected] to org.jclouds.http.HttpResponseException: request: HEAD https://my-backups.s3.amazonaws.com/snapshots/a3b72e7b-bd70-4f9e-aa2a-

cf6c2a5ff336/sstables/1458057843-my_ks-mytable-ka-57417-Index.db.gz HTTP/1.1 failed with response: HTTP/1.1 500 Internal Server Error at org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:63) at org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67) at org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:135) at org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:105) at org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.invoke(InvokeSyncToAsyncHttpMethod.java:128) at org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.apply(InvokeSyncToAsyncHttpMethod.java:94) at org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.apply(InvokeSyncToAsyncHttpMethod.java:55) at org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156) at org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123) at com.sun.proxy.$Proxy51.objectExists(Unknown Source) at org.jclouds.s3.blobstore.S3BlobStore.blobExists(S3BlobStore.java:175) at org.jclouds.blobstore2$blob_exists_QMARK_.invoke(blobstore2.clj:238) at opsagent.backups.destinations$create_blob.invoke(destinations.clj:48) at opsagent.backups.destinations$fn__12755.invoke(destinations.clj:185) at opsagent.backups.destinations$fn__12385$G__12378__12396.invoke(destinations.clj:25) at opsagent.backups.staging$start_staging_BANG_$fn__12925$state_machine__5264__auto____12926$fn__12931$fn__12962.invoke(staging.clj:61) at opsagent.backups.staging$start_staging_BANG_$fn__12925$state_machine__5264__auto____12926$fn__12931.invoke(staging.clj:59) at opsagent.backups.staging$start_staging_BANG_$fn__12925$state_machine__5264__auto____12926.invoke(staging.clj:56) at clojure.core.async.impl.ioc_macros$run_state_machine.invoke(ioc_macros.clj:940) at clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invoke(ioc_macros.clj:944) at clojure.core.async.impl.ioc_macros$take_BANG_$fn__5280.invoke(ioc_macros.clj:953) at clojure.core.async.impl.channels.ManyToManyChannel$fn__1785.invoke(channels.clj:102) at clojure.lang.AFn.run(AFn.java:24) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

1

详细说明:
的OpsCenter 5.2.4
DSE 4.8.2每个节点
数据大小〜130GB×3个节点×3直流
压缩和S3服务器端加密启用
JVM_OPTS =” $ JVM_OPTS -Xmx512M -Djclouds.mpu.parts.magnitude = 100000 -Djclouds.mpu.parts.size = 32000000“

回答

1

OpsCenter 5.2.4中存在一个问题,它将blob_exists代码放在我们的重试循环之外。这已在OpsCenter 6.0.1中得到解决。