When the sampling type is rate, the number of actual results is equal to the number of threads multiplied by the configured rate parameter

[huangjiecheng]

Describe the bug When using the ratelimit type, the actual number of sampled results is twice the expected

To Reproduce Steps to reproduce the behavior:

1. config file: jaeger_tracing_config.json {"service_name":"xxxx","disabled":false,"sampler":{"param":"5.0","type":"ratelimit"},"reporter":{"logSpans":true},"propagation_format":"w3c"} 2.nginx config file: opentracing_load_tracer /opt/cloud/resty/lib64/libjaegertracing_plugin.so /opt/cloud/resty/jaeger_tracing_config.json; 3.call API

Expected behavior The rate sampling should be consistent with the configuration parameters

Screenshots

Version (please complete the following information):

• OS: Linux
• Jaeger version: 1.23
• Deployment: Docker

What troubleshooting steps did you try?

Additional context