0

There is an issue regrading sockets that i am facing, assume we have two services running A and B and both services have 5 replicas. client is connected to service B and service B sends socket to service A. Initially assumption was service A pods are receiving 5 independent socket(because of 5 pods) and distribution lock was implemented but same issue was being replicated also injected pod information in node server after that we came to know same pod was receiving 5 sockets. also mentioning that redis-adptar pub/sub model is also implemented.

Improve this question
2
  • Can you edit the question to include a minimal reproducible example, and make it clearer what problem exactly you're running into? Assuming you have Services in front of both sets of Pods, the external client could hit any B instance which could connect to any A instance; if you need a distributed lock to ensure you're not doing parallel processing then just using a single replica would be simpler and more efficient. Commented Oct 14 at 13:12
  • @DavidMaze well i will create minimal reproducible example shortly but upon further investigation i found multiple connection of socket are being created. i guess its not related to K8. Commented Oct 14 at 14:33
Related questions
0
Redis connect ECONNREFUSED in NodeJS in Kubernetes cluster
1
GCP-LB unevenly distributing traffic to HAProxy Ingress Controller Pods
390
Command to delete all pods in all kubernetes namespaces
Load 6 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.