setToClient 先更新本地 mode,再尝试启动客户端。固定版本源码在缺少客户端 SPI 或启动异常时会返回 false,而模式字段不一定回滚。再次调用还可能命中“已经是客户端”的快速返回,不能只观察一个布尔值就认定集群限流可用。
无服务端配置时的实际检查
复用共享 POM,确保固定版本的 cluster-client-default 在类路径中。本例从全新 JVM 运行,未配置 token server,核对模式能启动但没有服务端地址。各测试类使用独立 fork,避免静态状态相互污染。
package site;
import com.alibaba.csp.sentinel.cluster.ClusterStateManager;
import com.alibaba.csp.sentinel.cluster.client.config.ClusterClientConfigManager;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.*;
class SentinelClientModeTest {
@Test void startingClientDoesNotProveServerConnectivity() {
try {
assertTrue(ClusterClientConfigManager.getServerHost()==null || ClusterClientConfigManager.getServerHost().isBlank());
assertTrue(ClusterStateManager.setToClient());
assertTrue(ClusterStateManager.isClient());
System.out.println("client-mode=true; configured-server=false; token-request-tested=false");
} finally { ClusterStateManager.applyState(ClusterStateManager.CLUSTER_NOT_STARTED); }
}
}
mvn -Dtest=SentinelClientModeTest test
实际结果与边界
本次输出 client-mode=true; configured-server=false; token-request-tested=false。它明确说明“处于客户端模式”与“已经连接并获取配额”是两项检查。要继续做完整集群限流实验,还需要服务端地址、规则 flowId、命名空间、阈值类型及请求结果验证。
客户端无法取得服务端结果时的本地回退由规则配置决定,不能把所有异常都写成无条件放行或无条件拒绝。本轮没有远程 token 请求、失败回退或配额分布测试;旧 NettyTransportClient 截图只作历史调用链材料。
下一步阅读
原资料片段(未重建原环境)
下方保留原资料的上下文、示例与截图;本轮验证只对应上方新增文件,未将旧运行结果记为本轮结果。
public static boolean setToClient() {
if (mode == CLUSTER_CLIENT) {
return true;
}
mode = CLUSTER_CLIENT;
sleepIfNeeded();
lastModified = TimeUtil.currentTimeMillis();
return startClient();
}
private static boolean startClient() {
try {
EmbeddedClusterTokenServer server = EmbeddedClusterTokenServerProvider.getServer();
if (server != null) {
server.stop();
}
//!!!
ClusterTokenClient tokenClient = TokenClientProvider.getClient();
if (tokenClient != null) {
tokenClient.start();
RecordLog.info("[ClusterStateManager] Changing cluster mode to client");
return true;
} else {
RecordLog.warn("[ClusterStateManager] Cannot change to client (no client SPI found)");
return false;
}
} catch (Exception ex) {
RecordLog.warn("[ClusterStateManager] Error when changing cluster mode to client", ex);
return false;
}
}

spiclient配置


DefaultClusterTokenClient
//client属性
private ClusterTransportClient transportClient;
//启动
@Override
public void start() throws Exception {
if (shouldStart.compareAndSet(false, true)) {
startClientIfScheduled();
}
}
private void startClientIfScheduled() throws Exception {
if (shouldStart.get()) {
if (transportClient != null) {
//调用client start方法
transportClient.start();
} else {
RecordLog.warn("[DefaultClusterTokenClient] Cannot start transport client: client not created");
}
}
}
public DefaultClusterTokenClient() {
ClusterClientConfigManager.addServerChangeObserver(new ServerChangeObserver() {
@Override
public void onRemoteServerChange(ClusterClientAssignConfig assignConfig) {
changeServer(assignConfig);
}
});
//在构造方法中会初始化client
initNewConnection();
}
private void initNewConnection() {
if (transportClient != null) {
return;
}
String host = ClusterClientConfigManager.getServerHost();
int port = ClusterClientConfigManager.getServerPort();
if (StringUtil.isBlank(host) || port <= 0) {
return;
}
try {
//client 是netty client
this.transportClient = new NettyTransportClient(host, port);
this.serverDescriptor = new TokenServerDescriptor(host, port);
RecordLog.info("[DefaultClusterTokenClient] New client created: {}", serverDescriptor);
} catch (Exception ex) {
RecordLog.warn("[DefaultClusterTokenClient] Failed to initialize new token client", ex);
}
}
版权声明:本文不是「本站」原创文章,版权归原作者所有 | 原文地址: