k8s集群中的通信
k8s集群中的通信
提问于 2018-05-08 09:04:29
我有一个由2个hazelcast实例和一个客户端应用程序组成的k8s集群。目标是拥有许多客户和至少2名哈泽尔广播公司成员。我在LoadBalancer中设置了一个k8s类型服务来公开hazelcast实例
apiVersion: v1
kind: Service
metadata:
name: hazelcast-service
labels:
app: hazelcast-service
spec:
type: LoadBalancer
ports:
- port: 10236
targetPort: 5701
selector:
app: hazelcast 当客户端从给定的配置开始时：
clientConfig.getNetworkConfig().addAddress("127.0.0.1:10236");承认哈泽尔广播的成员：
May 08, 2018 11:25:21 AM com.hazelcast.core.LifecycleService
INFO: hz.client_0 [dev] [3.9.3] HazelcastClient 3.9.3 (20180216 - 539b124) is STARTING
May 08, 2018 11:25:22 AM com.hazelcast.core.LifecycleService
INFO: hz.client_0 [dev] [3.9.3] HazelcastClient 3.9.3 (20180216 - 539b124) is STARTED
May 08, 2018 11:25:22 AM com.hazelcast.client.connection.ClientConnectionManager
INFO: hz.client_0 [dev] [3.9.3] Trying to connect to [127.0.0.1]:10236 as owner member
May 08, 2018 11:25:22 AM com.hazelcast.client.connection.ClientConnectionManager
INFO: hz.client_0 [dev] [3.9.3] Authenticated with server [10.1.0.151]:5701, server version:3.10 Local address: /127.0.0.1:60102
May 08, 2018 11:25:22 AM com.hazelcast.client.spi.impl.ClientMembershipListener
INFO: hz.client_0 [dev] [3.9.3]
Members [2] {
Member [10.1.0.148]:5701 - b0e4a52f-0170-47f2-8ff3-74d9b67f45f5
Member [10.1.0.151]:5701 - 1355caa4-5c2b-4366-bd5b-b504f4f0ae4f
}
May 08, 2018 11:25:22 AM com.hazelcast.client.connection.ClientConnectionManager
INFO: hz.client_0 [dev] [3.9.3] Setting ClientConnection{alive=true, connectionId=1, channel=NioChannel{/127.0.0.1:60102->/127.0.0.1:10236}, remoteEndpoint=[10.1.0.151]:5701, lastReadTime=2018-05-08 11:25:22.420, lastWriteTime=2018-05-08 11:25:22.418, closedTime=never, lastHeartbeatRequested=never, lastHeartbeatReceived=never, connected server version=3.10} as owner with principal ClientPrincipal{uuid='28696aaf-e678-47ee-8c7d-a79ba7a0079a', ownerUuid='1355caa4-5c2b-4366-bd5b-b504f4f0ae4f'}
May 08, 2018 11:25:22 AM com.hazelcast.core.LifecycleService
INFO: hz.client_0 [dev] [3.9.3] HazelcastClient 3.9.3 (20180216 - 539b124) is CLIENT_CONNECTED
May 08, 2018 11:25:22 AM com.hazelcast.internal.diagnostics.Diagnostics
INFO: hz.client_0 [dev] [3.9.3] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.当它试图连接到第二个实例(10.1.0.151)时，它似乎也很好：
May 08, 2018 11:25:29 AM com.hazelcast.core.LifecycleService
INFO: hz.client_1 [dev] [3.9.3] HazelcastClient 3.9.3 (20180216 - 539b124) is STARTING
May 08, 2018 11:25:29 AM com.hazelcast.core.LifecycleService
INFO: hz.client_1 [dev] [3.9.3] HazelcastClient 3.9.3 (20180216 - 539b124) is STARTED
May 08, 2018 11:25:29 AM com.hazelcast.client.connection.ClientConnectionManager
INFO: hz.client_1 [dev] [3.9.3] Trying to connect to [127.0.0.1]:10236 as owner member
May 08, 2018 11:25:29 AM com.hazelcast.client.connection.ClientConnectionManager
INFO: hz.client_1 [dev] [3.9.3] Authenticated with server [10.1.0.148]:5701, server version:3.10 Local address: /127.0.0.1:60113
May 08, 2018 11:25:29 AM com.hazelcast.client.spi.impl.ClientMembershipListener
INFO: hz.client_1 [dev] [3.9.3]
Members [2] {
Member [10.1.0.148]:5701 - b0e4a52f-0170-47f2-8ff3-74d9b67f45f5
Member [10.1.0.151]:5701 - 1355caa4-5c2b-4366-bd5b-b504f4f0ae4f
}
May 08, 2018 11:25:29 AM com.hazelcast.client.connection.ClientConnectionManager
INFO: hz.client_1 [dev] [3.9.3] Setting ClientConnection{alive=true, connectionId=1, channel=NioChannel{/127.0.0.1:60113->/127.0.0.1:10236}, remoteEndpoint=[10.1.0.148]:5701, lastReadTime=2018-05-08 11:25:29.455, lastWriteTime=2018-05-08 11:25:29.453, closedTime=never, lastHeartbeatRequested=never, lastHeartbeatReceived=never, connected server version=3.10} as owner with principal ClientPrincipal{uuid='a04aa2ca-626d-4d1a-a366-38c0dbc4781f', ownerUuid='b0e4a52f-0170-47f2-8ff3-74d9b67f45f5'}
May 08, 2018 11:25:29 AM com.hazelcast.core.LifecycleService
INFO: hz.client_1 [dev] [3.9.3] HazelcastClient 3.9.3 (20180216 - 539b124) is CLIENT_CONNECTED
May 08, 2018 11:25:29 AM com.hazelcast.internal.diagnostics.Diagnostics
INFO: hz.client_1 [dev] [3.9.3] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.但是，在收到上述消息后，我立即收到了另一条消息(似乎是关于我的客户端连接到的第一个成员的连接问题)：
Constructor threw exception; nested exception is com.hazelcast.core.OperationTimeoutException: ClientInvocation{clientMessage = ClientMessage{length=72, correlationId=272, operation=Client.createProxy, messageType=5, partitionId=-1, isComplete=true, isRetryable=false, isEvent=false, writeOffset=0}, objectName = hz:impl:mapService, target = address [10.1.0.151]:5701, sendConnection = null} timed out because exception occurred after client invocation timeout 120000 ms. Current time: 2018-05-08 11:27:29.913. Start time: 2018-05-08 11:25:29.458. Total elapsed time: 120455 ms.有时它甚至无法连接到第一个成员，因为我得到了OperationTimeoutException之后，客户端说它连接到10.1.0.151成员。有趣的是，有时它可以很好地工作：(当我只有一个哈泽尔广播吊舱的复制品时，它的工作是可预测的&很好。)因此，我认为这是因为LoadBalancer服务在目标荚之间平均分配请求，并且这种设置有问题。
我认为客户机应该能够连接到它想要的任何节点，因为任何节点都可以在其映射中存储请求的项，但是我不知道如何在k8s中设置这样的配置。
问题是:我应该如何在k8s中配置服务，以便客户端应用程序可以与所有成员对话？或者不是这样，它应该以另一种方式工作？
我是不是遗漏了什么？
回答 2
Stack Overflow用户
回答已采纳
发布于 2018-05-08 12:33:09
如果您的hazelcast客户端位于kubernetes集群中，则不需要LoadBalancer类型。一个简单的服务ClusterIP或无头服务就足够了。Hazelcast支持kubernetes的发现模式。我建议您尝试使用ClusterIP或none。
Stack Overflow用户
发布于 2018-05-08 12:18:43
因此，我认为这是因为LoadBalancer服务在目标荚之间平均分配请求，并且这种设置有问题。
是的，这是真的。
我应该如何在k8s中配置服务，以便客户端应用程序可以与所有成员对话？
服务只能在可用的豆荚之间平衡请求。
或者不是这样，它应该以另一种方式工作？
是的，这是个好主意。最简单的方法是为每个hazelcast副本创建一个服务。而这实际上是唯一的方法。
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/50229891
复制相关文章
相似问题
腾讯云开发者
