[
https://issues.apache.org/jira/browse/FLINK-37351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054925#comment-18054925
]
Rion Williams commented on FLINK-37351:
---------------------------------------
[~arvid]
I've gone ahead and issued a proposed PR for the implementation of the
suggested co-location (e.g., detect toplogy and leverage a co-location group
key) along with a series of test to verify behavior. I've tagged you on it for
review and would happily welcome and suggestions or feedback, or to highlight
any other areas that may need to be addressed.
* [https://github.com/apache/flink/pull/27486]
> Ensure writer and committer are colocated
> -----------------------------------------
>
> Key: FLINK-37351
> URL: https://issues.apache.org/jira/browse/FLINK-37351
> Project: Flink
> Issue Type: Bug
> Components: API / Core
> Affects Versions: 2.1.0
> Reporter: Arvid Heise
> Priority: Major
> Labels: pull-request-available
>
> Writer and committer should always be co-located in sinks that do not have a
> pre-commit topology to improve performance and potentially allow backchannels
> (in the style of statefun) to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
