TrinityClient fails when connect to GE Service Fabric App
TaviTruman opened this issue · 2 comments
The TrinityClient (Service Fabric Remoting) seems to work as expected in a service-to-service use-case but it does not work from an external client. After months of development and testing, we finally have a GE App Server working reliably in an SF Cluster - great work via Yatao. If the GE Team does not have the cycles to look into this problem please let me know so that I can dedicate members from my dev team to debug and fix this.
Here some additional information for debugging:
UPDATE: the current implementation of the TrinityClient (SF Remoting Client) for Service Fabric only works within a cluster so that you can communicate between GE/SF services; the demo in the "GraphEngine.ServiceFabric" project is a good place to start. I've written a new Native Trinity Service Fabric Client that will connect from outside of the GE/cluster. This is a sophisticated SF Cluster setup; X509 Certificate and Reverse Proxy configuration in the Windows Server 2019 DataCenter Standalone Cluster. Preliminary test results are positive but I still have a few issues to resolve.