[
https://issues.apache.org/jira/browse/NIFI-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575929#comment-17575929
]
Malthe Borch commented on NIFI-10313:
-------------------------------------
Actually, the service object is configured with ClientIP-based session
affinity, relevant snippet:
{code:java}
apiVersion: v1
kind: Service
spec:
sessionAffinity: ClientIP
sessionAffinityConfig:
clientIP:
timeoutSeconds: 10800
type: LoadBalancer{code}
That is, it should already have a 3-hour affinity to a single pod in the
statefulset.
I checked just now again with 1.16.3 and here there is no problem with our
configuration.
> Unexpected "Access Token not found"
> -----------------------------------
>
> Key: NIFI-10313
> URL: https://issues.apache.org/jira/browse/NIFI-10313
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.17.0
> Reporter: Malthe Borch
> Assignee: David Handermann
> Priority: Major
> Attachments: NiFi-Errors.PNG, authorizers.xml, nifi.log
>
>
> I'm experiencing some unexpected "Access Token not found" errors after
> upgrading to 1.17.0.
> See attached traceback.
> What happens is that the NiFi UI seems to work but after a short while the
> view is redirected to a conflict page (Unable to communicate with NiFi).
> There are no other problems or evidence of the issue to be found in the logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
