jackwener commented on a change in pull request #7654:
URL: https://github.com/apache/incubator-doris/pull/7654#discussion_r780679573
##########
File path: docs/zh-CN/faq/faq.md
##########
@@ -341,3 +341,76 @@ failed to initialize storage reader.
tablet=63416.1050661139.aa4d304e7a7aff9c-f0
这是 bdbje 的一个 bug，尚未解决。遇到这种情况，只能通过
[元数据运维手册](../administrator-guide/operation/metadata-operation.md) 中的 故障恢复
进行操作来恢复元数据了。
+### Q24. 多个FE，在使用Nginx实现web UI负载均衡的时候，登录不进去的情况
+
+Doris 可以部署多个FE，在访问Web
UI的时候，如果使用Nginx进行负载均衡，因为Session问题会出现不停的提示要重新登录，这个问题其实是Session共享的问题，Nginx提供了集中Session共享的解决方案，这里我们使用的是nginx中的ip_hash技术，ip_hash能够将某个ip的请求定向到同一台后端，这样一来这个ip下的某个客户端和某个后端就能建立起稳固的session，ip_hash是在upstream配置中定义的：
+
+```
+upstream doris.com {
+ server 172.22.197.238:8030 weight=3;
+ server 172.22.197.239:8030 weight=4;
+ server 172.22.197.240:8030 weight=4;
+ ip_hash;
Review comment:
```suggestion
server 172.22.197.238:8030 weight=3;
server 172.22.197.239:8030 weight=4;
server 172.22.197.240:8030 weight=4;
ip_hash;
```
##########
File path: docs/en/faq/faq.md
##########
@@ -340,3 +340,77 @@ To ensure the unique data order between different
replicas, refer to the [Seque
Sometimes when restarting the Fe, the above error will occur (usually only in
the case of multiple followers), and the difference between the two values in
the error is 2. As a result, the Fe startup fails.
This is a bug in bdbje that has not been resolved. In this case, metadata can
only be recovered through fault recovery in [metadata operation and maintenance
manual](../administrator-guide/operation/metadata-operation.md).
+
+### Q24. Multiple FEs, when using Nginx to implement web UI load balancing,
the login cannot be entered
+
+Doris can deploy multiple FEs. When accessing the Web UI, if you use Nginx for
load balancing, you will be prompted to log in again because of Session
problems. This problem is actually a session sharing problem. Nginx provides
centralized session sharing. The solution, here we use the ip_hash technology
in nginx, ip_hash can direct the request of a certain ip to the same backend,
so that a certain client and a certain backend under this ip can establish a
stable The session, ip_hash is defined in the upstream configuration:
+
+```
+upstream doris.com {
+ server 172.22.197.238:8030 weight=3;
+ server 172.22.197.239:8030 weight=4;
+ server 172.22.197.240:8030 weight=4;
+ ip_hash;
Review comment:
```suggestion
server 172.22.197.238:8030 weight=3;
server 172.22.197.239:8030 weight=4;
server 172.22.197.240:8030 weight=4;
ip_hash;
```
--
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: commits-unsubscr...@doris.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
