The Wayback Machine - https://web.archive.org/web/20210801060351/https://github.com/alibaba/nacos/issues/6200
Skip to content

/ nacos

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

Jump to bottom

nacos2.x在docker环境下集群部署，一直自动重启 #6200

Open
savvyray opened this issue Jun 29, 2021 · 6 comments · May be fixed by nacos-group/nacos-group.github.io#213
Open

nacos2.x在docker环境下集群部署，一直自动重启 #6200

savvyray opened this issue Jun 29, 2021 · 6 comments · May be fixed by nacos-group/nacos-group.github.io#213
Labels
good first issue

Comments

@savvyray
Copy link

@savvyray savvyray commented Jun 29, 2021

Both versions of nacos2.0.0 and nacos2.0.2 were tried, unable to cluster successfully under mac and centos, the log output service is being restarted, unable to start normally, and cannot complete the election.
尝试了nacos2.0.0和nacos2.0.2两个版本，在mac和centos下都无法集群成功，日志一直输出服务在重启，无法正常启动，也无法完成选举.
@savvyray
Copy link
Author

@savvyray savvyray commented Jun 29, 2021

The reason may be that due to lack of memory, other service can not start normally, and finally, the service reported wrong and restart all the time. By increasing docker, the service in the cluster can start normally, and finally solve the problem
原因可能是由于docker环境下，内存不足导致另外的服务无法正常启动，最后导致服务报错，一直重启，通过增大docker限制内存，使集群内的服务都正常启动，最终解决问题
@realJackSun
Copy link
Collaborator

@realJackSun realJackSun commented Jun 29, 2021

Thanks for sharing your fix case, we will Add this case into FAQ of nacos documentation, please copy this issue to the nacos document github repository.
https://github.com/nacos-group/nacos-group.github.io/issues
@shihap233
Copy link

@shihap233 shihap233 commented Jul 1, 2021

نعم. من المهم تقصي الحقيقه
@MaryJaneLove4
Copy link

@MaryJaneLove4 MaryJaneLove4 commented Jul 5, 2021

Důvodem může být to, že kvůli nedostatku paměti se jiná služba nemůže spustit normálně a nakonec služba nahlásila chybu a restartovala celou dobu. Zvýšením ukotvitelný panel, služba v clusteru lze spustit normálně, a konečně vyřešit problém
@andakumar
Copy link

@andakumar andakumar commented Jul 20, 2021

Nice
@Hackarking
Copy link

@Hackarking Hackarking commented Jul 27, 2021

Follow me Thank you 😂
@brotherlu-xcq brotherlu-xcq linked a pull request that will close this issue Jul 30, 2021
Open
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue
7 participants
@savvyray @realJackSun @MaryJaneLove4 @shihap233 @andakumar @Hackarking and others