[Bug] GUI: The login information has expired. Click OK to jump to the login page.

[josedev-union]

Search before asking

• I had searched in the issues and found no similar issues.

Version

2.1

What's Wrong?

I am not able to use Doris GUI because this message is popping up always from the start.

What You Expected?

The login session should be usable.

How to Reproduce?

• Login Doris GUI using root account.
• Right after login, it happens.

Anything Else?

I can ignore this tip by clicking cancel button and go to any page and this tip message will pop everytime. But sometimes the GUI works regardless of this message. So i think this expiration notification is false negative.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[greypale163]

我也存在同样的问题，不过找到了原因。我这里通过配置apisix路由进行访问，apisix的路由配置的上游服务里，设置的doris节点有3个，默认是带权轮询，这样设置后去访问doris就会出现登录即session过期的问题。
解决办法是apisix路由配置的上游服务设置改为一致性哈希，或访问节点只设置成1个。

[Asakiny]

基于Doris Operator部署的Doris on K8S，多fe的情况下，也会遇到这个bug，似乎需要设置svc的spec.sessionAffinity=ClusterIP来保持会话，但是发现目前的官方提供的doris helm不支持修改

[josedev-union]

我也存在同样的问题，不过找到了原因。我这里通过配置apisix路由进行访问，apisix的路由配置的上游服务里，设置的doris节点有3个，默认是带权轮询，这样设置后去访问doris就会出现登录即session过期的问题。 解决办法是apisix路由配置的上游服务设置改为一致性哈希，或访问节点只设置成1个。

do you mean you use apisix as the gateway infront of doris FE Or doris FE uses apisix as builtin?

[josedev-union]

基于Doris Operator部署的Doris on K8S，多fe的情况下，也会遇到这个bug，似乎需要设置svc的spec.sessionAffinity=ClusterIP来保持会话，但是发现目前的官方提供的doris helm不支持修改

I think your idea is to set ClientIP for sessionAffinity. Btw, this cannot be a perfect solution because normally FE is exposed using LoadBalancer service type or Ingress. In those cases, ClientIP is overridden by LB ip or ingress controller's ip.

[Asakiny]

在云环境下，您的观点是没问题的，通常私有环境部署是使用的是NodePort，Doris也提供了NodePort的配置方式，这种情况下既然提供了NodePort的配置方式，我理解对应的多fe的svc配置也是需要匹配的，目前我临时edit svc添加spec.sessionAffinity=ClusterIP是暂时可以解决的，仅供各位遇到同样问题可以参考。
In a cloud environment, your point is valid. Usually, in a private environment deployment, NodePort is used frequently, and Doris also provides a NodePort configuration method. In this case, since NodePort configuration is provided, I understand that the corresponding multi-FE svc configuration also needs to match. Currently, I temporarily edited the svc to add spec.sessionAffinity=ClusterIP, which can temporarily solve the problem. This is provided as a reference for anyone encountering the same issue.