Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix LinuxBrokerHostUsageImpl scheduled timer #113

Merged

Conversation

sschepens
Copy link
Contributor

Missed this in #88

@yahoocla
Copy link

CLA is valid!

@merlimat merlimat merged commit 3c596d4 into apache:master Nov 16, 2016
@sschepens sschepens deleted the fix_linux_host_usage_collection_timer branch November 16, 2016 19:23
sijie pushed a commit to sijie/pulsar that referenced this pull request Mar 4, 2018
hrsakai pushed a commit to hrsakai/pulsar that referenced this pull request Dec 10, 2020
Fixes apache#111
Subscriber.Subscription() should return the subscription name instead of returns ""
hangc0276 pushed a commit to hangc0276/pulsar that referenced this pull request May 26, 2021
…che#114)

Fix apache#113 
In current request handler. we passed in the request and after some handles return a responseFuture.
If several request comes in at same time, the handling time difference will cause the return future order different with the order that command comes in. And this will cause request handling order different.

This error is seen in the KafkaMessageOrderTest:
- client send 10 messges, while first 9 messages batched together, and the last one not batched;
- the above 2 request comes into handleProduceRequest, but the second request returned earlier than the first.

The fix is:
- add request response future in order at the time that request comes in, and call related handlers later.
- add produce request in order, and handle one by one in each channel. 

* add request response future at the time request comes
* make produce request in order
* change cursor delete to async in KafkaTopicConsumerManager
* add some logs of offset
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants