ping request
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by tracing the MQTT proxy ping request and response flow described in the issue. Reproduce the behavior with a client subscribed to many topics and compare direct proxy responses with broker-forwarded responses. Done means one agreed approach reduces unnecessary broker or client ping traffic without breaking MQTT ping behavior.
Written by the indexing model from the issue text.
Description
Is your enhancement request related to a problem? Please describe.
Current： when using mqtt proxy, client will send ping request to proxy , then proxy will send this request to broker. when broker receives this ping request , it will return repsonse to proxy, and proxy will write this response to client.
Question: if a client has thusands of topics, proxy will write many ping requests to broker, then proxy will receive many responses. of course ,this client will also receive many ping responses.
Describe the solution you'd like
- Is it possible to consider returing ping response to client directly at the proxy node?
- or can we deduplicate the ping response on the proxy side to avoid sending many response to the client?
- Dominant language
- Java
- Stars
- 190
- Forks
- 56
- Avg merge
- 27m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from streamnative/mop
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
streamnative/mop#1868 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
streamnative/mop#1818 · 1 comment ·
-
Can not build mop Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
streamnative/mop#1765 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
streamnative/mop#1758 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
streamnative/mop#1665 ·
All issues in streamnative/mop
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
area/frontend
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100