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
with multi producers to send message to multi cluster, all of which have enabled the message trace feature. Only the first producer sends message trace message succeed.
What did you do (The steps to reproduce)?
init many producers connected to different clusters, and send message to different clusters.
What did you expect to see?
all clusters with message trace message in.
What did you see instead?
only the first initialized producer sent message trace message succeed.
Please tell us about your environment:
develop branch
Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
1.revise AsyncTraceDispatcher implementation
FEATURE REQUEST
Please describe the feature you are requesting.
Provide any additional detail on your proposed use case for this feature.
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
BUG REPORT
What did you do (The steps to reproduce)?
init many producers connected to different clusters, and send message to different clusters.
What did you expect to see?
all clusters with message trace message in.
What did you see instead?
only the first initialized producer sent message trace message succeed.
Please tell us about your environment:
develop branch
Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
1.revise AsyncTraceDispatcher implementation
FEATURE REQUEST
Please describe the feature you are requesting.
Provide any additional detail on your proposed use case for this feature.
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
The text was updated successfully, but these errors were encountered: