[GitHub] kafka pull request #39: KAFKA-1833: OfflinePartitionLeaderSelector may retur...

2016-12-20 Thread tedxia
Github user tedxia closed the pull request at:

https://github.com/apache/kafka/pull/39


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-1834: No Response when handle LeaderAndI...

2014-12-28 Thread tedxia
GitHub user tedxia opened a pull request:

https://github.com/apache/kafka/pull/40

KAFKA-1834: No Response when handle LeaderAndIsrRequest some case

PR for [KAFKA-1834](https://issues.apache.org/jira/browse/KAFKA-1834)

When a replica become leader or follower, if this broker no exist in 
assigned replicas, there are no response.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tedxia/kafka 
fix-noresponse-on-become-leader-or-follower

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/40.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #40


commit 80858f72c39eaa974a6085f78e797de4e8c55aae
Author: xiajun 
Date:   2014-12-29T07:53:44Z

No Response when handle LeaderAndIsrRequest some case




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-1833: OfflinePartitionLeaderSelector may...

2014-12-28 Thread tedxia
GitHub user tedxia opened a pull request:

https://github.com/apache/kafka/pull/39

KAFKA-1833: OfflinePartitionLeaderSelector may return null leader when ISR 
and Assgi...

In OfflinePartitonLeaderSelector::selectLeader, when liveBrokerInIsr is not 
empty and have no common broker with liveAssignedreplicas, selectLeader will 
return no leader;

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tedxia/kafka fix-select-leader

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/39.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #39


commit 6f20bdc9ebe7b4a56de492c98e7a89ac7e3985ba
Author: xiajun 
Date:   2014-12-29T07:22:54Z

OfflinePartitionLeaderSelector may return null leader when ISR and Assgined 
Broker have no common broker




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---