[ https://issues.apache.org/jira/browse/FLINK-27933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552776#comment-17552776 ]
Chesnay Schepler edited comment on FLINK-27933 at 6/23/22 7:22 PM: ------------------------------------------------------------------- OperationResult made serializable: master: 72cc925a88ad054449f0ade9a476ead7a287cb6f 1.15: 0cd291ddae6581784e8d57e34fe3346607cb4f26 Additional safeguards: master: f2ef60c4fd5470995c4acd6e6f96c6cd6bde84c3 was (Author: zentol): 1.15: 0cd291ddae6581784e8d57e34fe3346607cb4f26 > Savepoint status cannot be queried from standby jobmanager > ---------------------------------------------------------- > > Key: FLINK-27933 > URL: https://issues.apache.org/jira/browse/FLINK-27933 > Project: Flink > Issue Type: Bug > Components: Runtime / Coordination > Affects Versions: 1.15.0 > Reporter: Chesnay Schepler > Assignee: Chesnay Schepler > Priority: Major > Labels: pull-request-available > Fix For: 1.16.0, 1.15.1 > > > The savepoint status handler currently doesn't work on standby dispatchers > because the OperationResult isn't serializable. > This wasn't caught by the recently added serialization safeguards, as those > only covered the caller side (i.e., arguments passed to callee), but not the > return value. -- This message was sent by Atlassian Jira (v8.20.7#820007)