-
Notifications
You must be signed in to change notification settings - Fork 103
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.
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
Etcd registry oom exception #272
Comments
This might the issue of etcd regsitry. Etcd regsitry has been moved to apache/dubbo-spi-extensions since apache dubbo 3.x. |
Can you pls reproduce it and provide the java dump? |
目前无法复现 |
我这又有一个新思路,我这个有问题的组件,除了dubbo会跟etcd频繁交互,业务本身也会创建etcdclient直接交互,结合上面的现象,是不是两个client都对到了同一个etcd server节点上导致了这个问题,dubbo-etcd-registry这边有什么相关bug嘛 |
What is the ETCD server version |
3.4.13 |
dubbo版本 2.7.23
组件A(两个节点)消费组件B(两个节点),当我给组件B扩容(新增两个节点,运行服务与存量节点无异)后,组件A的一个节点输出以下报错
![image](https://private-user-images.githubusercontent.com/45619625/293151290-7314213f-3521-459b-8ed4-1ef74a70e541.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk2NzM5NjUsIm5iZiI6MTcxOTY3MzY2NSwicGF0aCI6Ii80NTYxOTYyNS8yOTMxNTEyOTAtNzMxNDIxM2YtMzUyMS00NTliLThlZDQtMWVmNzRhNzBlNTQxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjI5VDE1MDc0NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQ2MDMyNjNlZmY2ZTJjMDhmN2ZiN2QzMzFiNGMzOTcxYWJiYjQyMjExMTA0OTgwZjJkZmM0YzA2NTlkZmJhOTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.lQ5Sf0CjBHI_GBuve4RVoUgwXUt2ERRe8JI9BG3A-GQ)
![image](https://private-user-images.githubusercontent.com/45619625/293151892-9132a45c-bd32-4523-813d-ae52fb696ea2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk2NzM5NjUsIm5iZiI6MTcxOTY3MzY2NSwicGF0aCI6Ii80NTYxOTYyNS8yOTMxNTE4OTItOTEzMmE0NWMtYmQzMi00NTIzLTgxM2QtYWU1MmZiNjk2ZWEyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjI5VDE1MDc0NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQxZjliNjIyY2M3Yjg4YTA0MzM4NWNiMDhiOWY4N2U3OGU3MDdmZTk5NDE1YTU3ZTRhZGQ5MDA3Nzc5MGQzZjcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.WnWWrFksabewVLIGBtpdlK_tfcbr1lxpdqBwWW_gi6U)
随后又持续输出以下报错
报错持续输出了4个小时,然后触发OOM,进程重启后恢复正常
The text was updated successfully, but these errors were encountered: