[
https://issues.apache.org/jira/browse/NIFI-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355542#comment-17355542
]
Chris Sampson commented on NIFI-8648:
-------------------------------------
[~jfrazee] I agree, some examples of common solutions would be a good idea -
such things are often asked about in the Slack channel and mailing lists, so
having them in the Admin Guide may reduce the frequency of such questions but
also give the community a place of reference to direct people towards.
In the couple of years I've been using NiFi, I don't think I've once seen
anyone asking about use of Apache httpd. I guess that could be because such
users have managed to find and use the example from the Admin Guide, but more
likely I'd guess that it's just not a solution of choice for most users (with
the move towards cloud technologies, I think httpd has probably fallen out of
favour somewhat with nginx/HAProxy becoming more ubiquitous - for example, the
standard ingress controller and service implementation in Kubernetes appears to
be nginx).
We probably want to be careful not to over-scope this documentation update
though - maybe this should be to add details and examples (common technologies)
of:
* Proxying user details with headers (like the current Admin Guide section)
* Session affinity/stickiness for load balancers (including reference to
ingress controllers)
Maybe a separate ticket would be good for adding some examples of
Kubernetes/Cloud setups in the future?
> Add session affinity info to proxy config section of admin guide
> ----------------------------------------------------------------
>
> Key: NIFI-8648
> URL: https://issues.apache.org/jira/browse/NIFI-8648
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Affects Versions: 1.13.2
> Reporter: Joey Frazee
> Priority: Minor
>
> When using proxies or load balancers with a cluster the user should use
> affinity or stickiness to assure that user sessions are consistent. This
> should be noted in the admin guide.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
