[
https://issues.apache.org/jira/browse/FLINK-25333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460256#comment-17460256
]
Seth Wiesman commented on FLINK-25333:
--------------------------------------
[~keremulutas] yes, that log line was actually the clue to me of what was
happening. You should never see that with a statefun application.
> Harden UID management when constructing statefun universe
> ---------------------------------------------------------
>
> Key: FLINK-25333
> URL: https://issues.apache.org/jira/browse/FLINK-25333
> Project: Flink
> Issue Type: Bug
> Components: Stateful Functions
> Reporter: Seth Wiesman
> Assignee: Seth Wiesman
> Priority: Major
> Labels: pull-request-available
> Fix For: statefun-3.2.0
>
>
> As described in this stack overflow, we do not set UIDs on routers. Because
> of how the stream graph is generated, the uids may be non-deterministic. We
> should manually set all UIDs and enforce this via configuration.
>
> https://stackoverflow.com/questions/70316498/flink-statefun-high-availability-exception-java-lang-illegalstateexception-th
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
