wolfboys commented on issue #3013: URL: https://github.com/apache/incubator-streampark/issues/3013#issuecomment-1712358389
>  > > By reviewing the relevant source code and Flink official documents, I believe that the correct savepoint format should be Format 1 in the screenshot > > So I think this should be a problem with Flink, not Streampark。To prove this, I ran the following test > > Flink Version 1.17.1 > > 1. Use HDFS to store the savepoint, and use the sp recovery task in format 1 as shown in the screenshot. Test result successful > 2. Use S3 to store the savepoint and select the s3a protocol, and use the sp restore task of format 1 in the screenshot. Test result successful > 3. Use S3 to store the savepoint and select the s3p protocol, and use the sp restore task of format 1 in the screenshot. test result failed > 4. Use S3 to store the savepoint and select the s3p protocol, and use the sp recovery task in format 2 in the screenshot. Test result successful > > In summary, it should be that flink sp has unexpected behavior when using S3 storage and using the s3p protocol > > If this is the design goal of flink, then maybe streampark needs to be optimized specifically for this scenario. If this does not meet the design goals of flink, it seems that the BUG should be reported to the flink community > > @wolfboys Sorry for taking so long to get back here, based on your description, there is a preliminary suspicion that it might be a bug in Flink. We need further confirmation. If it is true, we can provide feedback to the Flink community. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
