0

当我尝试使用 Cassy 进行备份、增量备份和一致性备份并恢复它们时，我可以检查所有操作是否成功。因为我可以在我的 S3 上看到所有类型的备份和恢复的数据。但是在 Cassy Logs 上，我每次备份时都可以看到 Warinig 日志。有什么问题吗？你介意告诉我如何解决警告吗？

贝娄是日志。

[centos@cassy-1 provision]$ docker exec -it provision_cassy_1 cat /var/log/scalar/cassy.log
2020-07-13 07:28:00.681 [pool-43-thread-1] INFO  n.s.sshj.transport.TransportImpl - Client identity string: SSH-2.0-SSHJ_0.27.0
2020-07-13 07:28:00.682 [pool-43-thread-3] INFO  n.s.sshj.transport.TransportImpl - Client identity string: SSH-2.0-SSHJ_0.27.0
2020-07-13 07:28:00.683 [pool-43-thread-2] INFO  n.s.sshj.transport.TransportImpl - Client identity string: SSH-2.0-SSHJ_0.27.0
2020-07-13 07:28:00.691 [pool-43-thread-1] INFO  n.s.sshj.transport.TransportImpl - Server identity string: SSH-2.0-OpenSSH_7.4
2020-07-13 07:28:00.696 [pool-43-thread-2] INFO  n.s.sshj.transport.TransportImpl - Server identity string: SSH-2.0-OpenSSH_7.4
2020-07-13 07:28:00.708 [pool-43-thread-3] INFO  n.s.sshj.transport.TransportImpl - Server identity string: SSH-2.0-OpenSSH_7.4
2020-07-13 07:28:01.182 [pool-43-thread-2] INFO  n.s.s.c.c.direct.SessionChannel - Will request `sftp` subsystem
2020-07-13 07:28:01.273 [pool-43-thread-2] INFO  c.s.c.r.RemoteCommandExecutor - executing /opt/cassy/bin/cassy-backup --cluster-id=ScalarDL-9136173c-6d0d-47c4-aece-1ab91c4f88d1 --snapshot-id=c5337eb5-debf-4b55-9b3f-41abee6de872 --target-ip=10.42.2.92 --data-dir=/data --store-base-uri=s3://scalar-terraform-cassy-bkup-backet --store-type=AWS_S3 --keyspaces=coordinator,system_distributed,system,system_schema,reaper_db,system_auth,system_traces,scalar --backup-type=2 in 10.42.2.92
2020-07-13 07:28:01.331 [pool-43-thread-1] INFO  n.s.s.c.c.direct.SessionChannel - Will request `sftp` subsystem
2020-07-13 07:28:01.366 [pool-43-thread-1] INFO  c.s.c.r.RemoteCommandExecutor - executing /opt/cassy/bin/cassy-backup --cluster-id=ScalarDL-9136173c-6d0d-47c4-aece-1ab91c4f88d1 --snapshot-id=c5337eb5-debf-4b55-9b3f-41abee6de872 --target-ip=10.42.2.46 --data-dir=/data --store-base-uri=s3://scalar-terraform-cassy-bkup-backet --store-type=AWS_S3 --keyspaces=coordinator,system_distributed,system,system_schema,reaper_db,system_auth,system_traces,scalar --backup-type=2 in 10.42.2.46
2020-07-13 07:28:01.384 [pool-43-thread-3] INFO  n.s.s.c.c.direct.SessionChannel - Will request `sftp` subsystem
2020-07-13 07:28:01.415 [pool-43-thread-3] INFO  c.s.c.r.RemoteCommandExecutor - executing /opt/cassy/bin/cassy-backup --cluster-id=ScalarDL-9136173c-6d0d-47c4-aece-1ab91c4f88d1 --snapshot-id=c5337eb5-debf-4b55-9b3f-41abee6de872 --target-ip=10.42.2.173 --data-dir=/data --store-base-uri=s3://scalar-terraform-cassy-bkup-backet --store-type=AWS_S3 --keyspaces=coordinator,system_distributed,system,system_schema,reaper_db,system_auth,system_traces,scalar --backup-type=2 in 10.42.2.173
2020-07-13 07:28:13.122 [pool-1-thread-1] INFO  n.s.sshj.transport.TransportImpl - Disconnected - BY_APPLICATION
2020-07-13 07:28:13.361 [pool-1-thread-1] INFO  n.s.sshj.transport.TransportImpl - Disconnected - BY_APPLICATION
2020-07-13 07:28:13.366 [pool-1-thread-1] INFO  n.s.sshj.transport.TransportImpl - Disconnected - BY_APPLICATION
2020-07-13 07:28:13.473 [pool-3-thread-1] WARN  c.s.c.server.CassyServerController - com.amazonaws.services.s3.model.AmazonS3Exception: Forbidden (Service: Amazon S3; Status Code: 403; Error Code: 403 Forbidden; Request ID: 7E3C55C561F61336; S3 Extended Request ID: /wnmbJya8WlQVkN/o1DDz/LVfeAReP79OWguM4ZplsxjNNkuvnnjnkW+m/P+cDZbSMEadpNBxUU=), S3 Extended Request ID: /wnmbJya8WlQVkN/o1DDz/LVfeAReP79OWguM4ZplsxjNNkuvnnjnkW+m/P+cDZbSMEadpNBxUU=
com.scalar.cassy.exception.FileTransferException: com.amazonaws.services.s3.model.AmazonS3Exception: Forbidden (Service: Amazon S3; Status Code: 403; Error Code: 403 Forbidden; Request ID: 7E3C55C561F61336; S3 Extended Request ID: /wnmbJya8WlQVkN/o1DDz/LVfeAReP79OWguM4ZplsxjNNkuvnnjnkW+m/P+cDZbSMEadpNBxUU=), S3 Extended Request ID: /wnmbJya8WlQVkN/o1DDz/LVfeAReP79OWguM4ZplsxjNNkuvnnjnkW+m/P+cDZbSMEadpNBxUU=
        at com.scalar.cassy.transferer.AwsS3FileUploader.requiresUpload(AwsS3FileUploader.java:107)
        at com.scalar.cassy.transferer.AwsS3FileUploader.upload(AwsS3FileUploader.java:43)
        at com.scalar.cassy.service.MetadataDbBackupService.backup(MetadataDbBackupService.java:43)
        at com.scalar.cassy.server.CassyServerController.lambda$backupMetadata$11(CassyServerController.java:450)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: Forbidden (Service: Amazon S3; Status Code: 403; Error Code: 403 Forbidden; Request ID: 7E3C55C561F61336; S3 Extended Request ID: /wnmbJya8WlQVkN/o1DDz/LVfeAReP79OWguM4ZplsxjNNkuvnnjnkW+m/P+cDZbSMEadpNBxUU=)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1712)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1367)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1113)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:770)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:744)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:726)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:686)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:668)
        at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:532)
        at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:512)
        at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4920)
        at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4866)
        at com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1320)
        at com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1294)
        at com.scalar.cassy.transferer.AwsS3FileUploader.requiresUpload(AwsS3FileUploader.java:97)
        ... 8 common frames omitted"
4

1 回答 1

0

我认为问题的发生是因为 Cassy master 无法访问 S3 以将其元数据存储为备份。（Cassy master 将其元数据同步到指定的云存储。）

所以发生的事情是，作为备份，它成功了，但它未能备份 Cassy master 中的元数据。备份元数据失败并不是很关键，因为元数据仍然保存在 Caasy 主磁盘的辅助磁盘中。但是当磁盘损坏时会出现问题，因为主服务器可能会丢失对备份的跟踪。

要解决这个问题，请为 Cassy 主节点分配适当的权限，以便它可以将一些数据写入 s3。

于 2020-07-20T00:36:57.923 回答