-
My running pulsar function is consuming data from a pulsar topic which is actually connected to kafka then store it into another one after processing. By the way, I have figured out that inRate and Out rate of both topic are varied across time and looks like batch model. So I want to know that there are any kinds of prcessing intervals or throttling parameters that process data like batch processing. This is the metrics that dashboard show me the which is IN/OUT rates of both topics. ( there is only one topic in each tenants )
What I think right is InRate of destination topic should be same with or close to OutRate of source topic . Here are more details that I captured in grafana dashboard. The first figure is about source topic's publish rate. And the second figure is about destination topic's publish rate Any kinds of comments would be appreciated to explain this merics that look like throlling mechanism. Thank you in advance |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Now I realize that IN-Rate of source topic is the main reason. The graph looks fine after I increase number of POD sto pull message from Kafka . |
Beta Was this translation helpful? Give feedback.
Now I realize that IN-Rate of source topic is the main reason.
The graph looks fine after I increase number of POD sto pull message from Kafka .