Comments (1)
비슷한 이슈
- 작업 중 브로커, 커넥트가 모두 정상일 때 커넥터 통신에서 timeout이 발생하면 이와 비슷한 이슈라고 생각하면 된다.
케이스
- 브로커를 재실행하거나, 특정 시점에 시스템 부하가 심해서, 특정 브로커와 토픽 간 연동이 실패했을 수 있다. 이럴 때, 정상 Running 상태처럼 보이지만, 연동 실패 상태가 지속되고, 커넥터 통신이 timeout 발생한다.
해결방안
- 브로커 재실행
- 스케일업, 스케일아웃
- 최적화 (kafka client가 제어가능한경우 consume, produce속도 조절 해주자.)
from simple-kafka-deploy.
Related Issues (6)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from simple-kafka-deploy.