-
Notifications
You must be signed in to change notification settings - Fork 51
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
long-time operation or many VMs may lead a meta db problem #1131
Comments
error handling 보완 필요. |
// GenMcisKey is func to generate a key used in keyValue store
} |
|
VM이 많이 포함된 MCIS에서, 내부 VM 정보를 삭제하면, MCIS 상태 조회 기능에서 오류 발생 가능. MCIS 상태 조회는 기본적으로 MCIS에 포함된 VM 리스트를 조회하여, MCIS 상태 조회가 길어지면, 결과적으로는 없는 VM에 대한 처리 요청이 발생할 수 있으며, |
MCIS 수를 300개까지 올려보면, Spider와의 connection 이슈로, hitting the default limit of 1024 "open files 발생함. 관련 솔루션: https://blog.sensecodons.com/2022/04/golang-httpclient-and-too-many-open.html 세션 확인하기 echo "cb-tb,cb-sp" > ss-tb.log; for run in {1..10000}; do cbtb=$(ss -anp | grep tumblebug | wc -l); cbsp=$(ss -anp | grep spider | wc -l); echo "${cbtb},${cbsp}" >> ss-tb.log; sleep 1; done |
미봉책: change max file descriptors https://stackoverflow.com/questions/32325343/go-tcp-too-many-open-files-debug ulimit 설정이 ubuntu 18.* 에서 오류가 있을 수 있음 |
고루틴 버퍼드 채널 사용 또는 https://dev.to/godoylucase/rate-limiting-your-goroutines-1om1 |
What happened
8개 MCIS, VM 100개 이상을 제어하는 상황에서,
MCIS의 개별 VM을 삭제한 후,
동일한 현상이 발생하는 MCIS가 있었음.
How to reproduce it (as minimally and precisely as possible)
Anything else we need to know?
:
Environment
Proposed solution
:
Any other context
:
The text was updated successfully, but these errors were encountered: