You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Danut Radoaica (Jira)" <ji...@apache.org> on 2021/05/10 10:02:00 UTC

[jira] [Created] (IGNITE-14695) .NET: communication problems between Apache Ignite server in Azure Kubernetes and thin clients in Azure Web Apps

Danut Radoaica created IGNITE-14695:
---------------------------------------

             Summary: .NET: communication problems between Apache Ignite server in Azure Kubernetes and thin clients in Azure Web Apps
                 Key: IGNITE-14695
                 URL: https://issues.apache.org/jira/browse/IGNITE-14695
             Project: Ignite
          Issue Type: Bug
          Components: platforms
    Affects Versions: 2.10
         Environment: Apache Ignite: v2.10.0

JDK: v1.8

.NET Core: v3.1
            Reporter: Danut Radoaica


If the Apache Ignite server and thin clients are in Azure Kubernetes there are no problems.

If the Apache Ignite server is in Azure Kubernetes and the thin clients are in Azure Web Apps (same subscription) we always receive this error: 

{ "Depth": 0, "ClassName": "System.IO.IOException", "Message": "Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond..", "Source": "System.Net.Sockets", "StackTraceString": " at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)\r\n at System.Net.Security.SslStream.FillBufferAsync[TReadAdapter](TReadAdapter adapter, Int32 minSize)\r\n at System.Net.Security.SslStream.ReadAsyncInternal[TReadAdapter](TReadAdapter adapter, Memory`1 buffer)\r\n at System.Net.Security.SslStream.Read(Byte[] buffer, Int32 offset, Int32 count)\r\n at Apache.Ignite.Core.Impl.Client.ClientSocket.SocketRead(Byte[] buf, Int32 pos, Int32 len)\r\n at Apache.Ignite.Core.Impl.Client.ClientSocket.ReceiveBytes(Int32 size)\r\n at Apache.Ignite.Core.Impl.Client.ClientSocket.ReceiveMessage()\r\n at Apache.Ignite.Core.Impl.Client.ClientSocket.SendRequest(RequestMessage& reqMsg)\r\n at Apache.Ignite.Core.Impl.Client.ClientSocket.DoOutInOp[T](ClientOp opId, Action`1 writeAction, Func`2 readFunc, Func`3 errorFunc)\r\n at Apache.Ignite.Core.Impl.Client.IgniteClient.GetOrCreateCache[TK,TV](CacheClientConfiguration configuration)\r\n at Druid.Ignite.CacheFactory.GetOrCreateCacheClient[TKey,TData](IIgniteClient ignite, String cacheName, Action`1 extendConfigurationAction)\r\n at Druid.Endpoints.Common.Utils.IgniteManager.GetOrCreateCacheClient[TKey,TData](String cacheName, Action`1 extendConfigurationAction) in /bigvol/azure.agents/bmagent03/_work/18/s/Druid.Endpoints.Common/Utils/IgniteManager.cs:line 28\r\n at Druid.Endpoints.Controllers.UiPathController.EventsJobCompleted(Nullable`1 paramBotId) in /bigvol/azure.agents/bmagent03/_work/18/s/Druid.Endpoints/Controllers/UiPathController.cs:line 374", "RemoteStackTraceString": null, "RemoteStackIndex": 0, "HResult": -2146232800, "HelpURL": null }, \{ "Depth": 1, "ClassName": "System.Net.Sockets.SocketException", "Message": "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.", "Source": "System.Net.Sockets", "StackTraceString": " at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)\r\n at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)", "RemoteStackTraceString": null, "RemoteStackIndex": 0, "HResult": -2147467259, "HelpURL": null }

 

Apache Ignite server: [https://github.com/dradoaica/AspNetCore.Ignite]

P.S.: is exposed from Kubernetes via:

apiVersion: v1
kind: Service
metadata:
 name: aspnetcoreignite-load-balancer-service
 namespace: develop
 annotations:
 external-dns.alpha.kubernetes.io/hostname: ignite.develop.aspnetcoreplatform.com
spec:
 selector:
 app: aspnetcoreignite
 ports:
 - name: jdbc
 protocol: TCP
 port: 11211
 targetPort: jdbc
 - name: comm-spi
 protocol: TCP
 port: 47100
 targetPort: comm-spi
 - name: disc-spi
 protocol: TCP
 port: 47500
 targetPort: disc-spi
 - name: jmx
 protocol: TCP
 port: 49112
 targetPort: jmx
 - name: sql
 protocol: TCP
 port: 10800
 targetPort: sql
 - name: rest-api
 protocol: TCP
 port: 8080
 targetPort: rest-api
 - name: thin-client
 protocol: TCP
 port: 10900
 targetPort: thin-client


 externalTrafficPolicy: Local
 type: LoadBalancer



--
This message was sent by Atlassian Jira
(v8.3.4#803005)