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
The actual cause is because of the default sampling rate value in helm chart is different from the docker setup, Raised a PR for this already
Hello All,
I've been following the steps and deploy social network with k8s and minikube using helm chart. And I have already tried 3 ways to forward the workloads to the nginx, but jaeger can only capture only a few traces (compared to docker using the exact same command).
For example: for 428 requests: docker: ~90 traces, k8s: ~10 traces
I have tried:
Port-forward: Use kubectl port-forward nginx-thrift-<id>-<id> 8080:8080
Node-Port: Add type: NodePort in the values.yaml of Nginx-thrift ( I changed the baseTemplate as well to ensure it works)
Loadbalancer: Add nginx-thrift type: LoadBalancer and then minikube tunnel
Put wrk2 into same cluster node: I make a pod based on the ubuntu-client.YAML in openshift. Run the script. Managed to send it successfully, but jaeger still only captures a few traces
I can access the application with all three methods mentioned above. But when I run the command ../wrk2/wrk -D exp -t 5 -c 5 -d 20 -L -s ./wrk2/scripts/social-network/compose-post.lua http://localhost:8080/wrk2-api/post/compose -R 20, it only shows a few traces.
But the wrk2 output seems show all request has been made successfully?
Although one way to get around may be set up k8s on bare metal machine, but I don't have the resources to do right now.
Does anyone know how to resolve this without setting up k8s on bare metal machine?
Thanks!
PS: The summary of my system (POP_OS based on ubuntu 22.04 LTS)
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
CPU family: 6
Model: 142
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
Stepping: 12
CPU max MHz: 4600.0000
CPU min MHz: 400.0000
BogoMIPS: 3999.93
The text was updated successfully, but these errors were encountered:
SkollRyu
changed the title
[social media network] Workloads die out, jaeger can only capture a few traces with k8s & minikube deployment
[social network] Workloads die out, jaeger can only capture a few traces with k8s & minikube deployment
Nov 7, 2023
The actual cause is because of the default sampling rate value in helm chart is different from the docker setup, Raised a PR for this already
Hello All,
I've been following the steps and deploy social network with k8s and minikube using helm chart. And I have already tried 3 ways to forward the workloads to the nginx, but jaeger can only capture only a few traces (compared to docker using the exact same command).
For example: for 428 requests: docker: ~90 traces, k8s: ~10 traces
I have tried:
kubectl port-forward nginx-thrift-<id>-<id> 8080:8080
type: NodePort
in the values.yaml of Nginx-thrift ( I changed the baseTemplate as well to ensure it works)type: LoadBalancer
and thenminikube tunnel
ubuntu-client.YAML
in openshift. Run the script. Managed to send it successfully, but jaeger still only captures a few tracesI can access the application with all three methods mentioned above. But when I run the command
../wrk2/wrk -D exp -t 5 -c 5 -d 20 -L -s ./wrk2/scripts/social-network/compose-post.lua http://localhost:8080/wrk2-api/post/compose -R 20
, it only shows a few traces.But the wrk2 output seems show all request has been made successfully?
Although one way to get around may be set up k8s on bare metal machine, but I don't have the resources to do right now.
Does anyone know how to resolve this without setting up k8s on bare metal machine?
Thanks!
PS: The summary of my system (POP_OS based on ubuntu 22.04 LTS)
The text was updated successfully, but these errors were encountered: