企业官网建设流程全解析

上一篇【第64篇】Netty生产问题排查——OOM/CPU飙高/连接泄漏全解析
下一篇【第66篇】Netty监控与可观测性——Metrics/Tracing/Logging全覆盖

一、熔断器模式

publicclassCircuitBreakerHandlerextendsChannelInboundHandlerAdapter{privatefinalAtomicIntegerfailures=newAtomicInteger();privatefinalintthreshold=10;// 10次失败熔断privatefinallongrecoveryTime=30000;// 30秒恢复privatelonglastFailureTime;privateStatestate=State.CLOSED;enumState{CLOSED,OPEN,HALF_OPEN}@OverridepublicvoidchannelRead(ChannelHandlerContextctx,Objectmsg){if(state==State.OPEN){if(System.currentTimeMillis()-lastFailureTime>recoveryTime){state=State.HALF_OPEN;// 尝试恢复}else{ctx.writeAndFlush("Service unavailable");return;}}try{doBusiness(msg);state=State.CLOSED;failures.set(0);}catch(Exceptione){if(failures.incrementAndGet()>=threshold){state=State.OPEN;lastFailureTime=System.currentTimeMillis();System.out.println("Circuit breaker OPEN!");}}}}

二、限流集成

// 令牌桶限流publicclassRateLimiterHandlerextendsChannelInboundHandlerAdapter{privatefinalRateLimiterlimiter=RateLimiter.create(1000);// 1000 QPSpublicvoidchannelRead(ChannelHandlerContextctx,Objectmsg){if(limiter.tryAcquire()){ctx.fireChannelRead(msg);// 放行}else{ctx.writeAndFlush("Rate limited, try again later");}}}

三、连接数限制

publicclassMaxConnectionHandlerextendsChannelInboundHandlerAdapter{privatefinalAtomicIntegerconnections=newAtomicInteger();privatefinalintmax=10000;publicvoidchannelActive(ChannelHandlerContextctx){if(connections.incrementAndGet()>max){System.out.println("连接数超限: "+max);ctx.close();// 拒绝新连接}}publicvoidchannelInactive(ChannelHandlerContextctx){connections.decrementAndGet();}}

四、降级策略

上一篇【第64篇】Netty生产问题排查——OOM/CPU飙高/连接泄漏全解析
下一篇【第66篇】Netty监控与可观测性——Metrics/Tracing/Logging全覆盖