akalash commented on pull request #17238: URL: https://github.com/apache/flink/pull/17238#issuecomment-920785097
> What are the alternative solutions? Can we for example ignore the newBufferSize messages if the upstream is not read, while caching it in the RemoteInputChannel and re-sending it in RemoteInputChannel#requestSubpartition/RemoteInputChannel#retriggerSubpartitionRequest? The problem is we don't know on the downstream side that the upstream isn't ready yet. So technically, the downstream can understand that the upstream is ready by receiving the any first message(for example. BacklogAnnouncement) from it. But it requires the extra flag which we should always check that is not good. So the second idea is to create a new message something like ReadinessAnnouncment which will be sent from the upstream to downstream when the reader is finally ready. And the downstream indeed can resend the last buffer size. -- 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]
