Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

客户端经常报com.alibaba.nacos.api.exception.NacosException: java.util.concurrent.TimeoutException: Waited 3000 milliseconds异常,改配置后发现效果很随机 #12613

Closed
besthanliu opened this issue Sep 5, 2024 · 5 comments
Closed

客户端经常报com.alibaba.nacos.api.exception.NacosException: java.util.concurrent.TimeoutException: Waited 3000 milliseconds异常,改配置后发现效果很随机 #12613

besthanliu opened this issue Sep 5, 2024 · 5 comments
Labels
status/duplicate This issue or pull request already exists

Comments

@besthanliu
Copy link

besthanliu commented Sep 5, 2024 •
edited
Loading

这个配置的生效有点随机
image
image
image
image

我通过java opt加入这些参数把超时配低方便触发,现在看到有时候有效是1000ms,有时候还是3000ms,改成5000ms也一样, 多个pod已经改了跑一个月了
@XiaZhouxx
Copy link
Contributor

看一下nacos的remote.log呢 客户端打印的日志看不出来是哪个没生效吧

@besthanliu besthanliu changed the title 客户端经常报com.alibaba.nacos.api.exception.NacosException: java.util.concurrent.TimeoutException: Waited 3000 milliseconds异常,改配置后发现效果粉碎机 客户端经常报com.alibaba.nacos.api.exception.NacosException: java.util.concurrent.TimeoutException: Waited 3000 milliseconds异常,改配置后发现效果很随机 Sep 6, 2024
@besthanliu
Copy link
Author

besthanliu commented Sep 6, 2024 •
edited
Loading

看一下nacos的remote.log呢 客户端打印的日志看不出来是哪个没生效吧

@XiaZhouxx 请问如何查看,是去看服务端的remote.log吗? 客户端部署在docker,请问路径是?

@XiaZhouxx
Copy link
Contributor

老哥我复现了, 应该就是历史遗留问题或者设计如此？因为client sdk 包含了服务注册和配置中心, 各自对于请求超时的需求不同导致的, 目前发现的就是ClientWorker配置中心的某些grpc请求timeout被定义死导致的

@besthanliu
Copy link
Author

besthanliu commented Sep 6, 2024 •
edited
Loading

@XiaZhouxx 哦,就是那个代码写死3000ms的那个ClientWorker对吧.应该属于历史遗留, timeout可配置应该才属于正常表现. 好的, 既然是那个代码的问题, 后续如果有优化版本, 可以在这个帖子回我一下吗?方便我去升级, 谢谢

@KomachiSion
Copy link
Collaborator

duplicate with #12103

@KomachiSion KomachiSion closed this as not planned Won't fix, can't repro, duplicate, stale Sep 6, 2024
@KomachiSion KomachiSion added the status/duplicate This issue or pull request already exists label Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status/duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@XiaZhouxx @KomachiSion @besthanliu