You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Has anyone been able to host an Akka actor inside a DaemonSet? What was your YAML configuration? Any example would be much appreciated!
We were successful at deploying multiple Akka services in their own StatefulSet pods but we have not been able to find the correct configuration to switch one of our service to a DaemonSet instead.
The pod that is now deployed in a DaemonSet is no longer reachable by the LightHouse pods. See error below
[WARNING][02/09/2021 22:04:17][Thread 0014][akka.tcp://[email protected]:9600/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2Fedgraphjobs%jobprocessor-svc-v1-s9899.jobprocessor-svc%3A9600-9690/endpointWriter] AssociationError [akka.tcp://[email protected]:9600] -> akka.tcp://[email protected]:9600: Error [Association failed with akka.tcp://[email protected]:9600] []
[WARNING][02/09/2021 22:04:17][Thread 0014][remoting (akka://edgraphjobs)] Tried to associate with unreachable remote address [akka.tcp://[email protected]:9600]. Address is now gated for 5000 ms, all messages to this address will be delivered to dead letters. Reason: [Association failed with akka.tcp://[email protected]:9600] Caused by: [System.AggregateException: One or more errors occurred. (Name or service not known)
---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (00000005, 0xFFFDFFFF): Name or service not known
at System.Net.Dns.InternalGetHostByName(String hostName)
at System.Net.Dns.ResolveCallback(Object context)
Here is the YAML configuration for the JobProcessor service (which was previously working as a StatefulSet)
HI,
Has anyone been able to host an Akka actor inside a DaemonSet? What was your YAML configuration? Any example would be much appreciated!
We were successful at deploying multiple Akka services in their own StatefulSet pods but we have not been able to find the correct configuration to switch one of our service to a DaemonSet instead.
The pod that is now deployed in a DaemonSet is no longer reachable by the LightHouse pods. See error below
Here is the YAML configuration for the JobProcessor service (which was previously working as a StatefulSet)
The text was updated successfully, but these errors were encountered: