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.

Sign up for GitHub

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

Jump to bottom

Handle keyed producer failover #314

Merged
merged 7 commits into from
Feb 20, 2015
Merged

Handle keyed producer failover #314

merged 7 commits into from
Feb 20, 2015

Conversation

dpkp
Copy link
Owner

@dpkp dpkp commented Feb 6, 2015

this is a test for issue #313 -- first step to fixing!

@coveralls
Copy link

Coverage Status

Coverage increased (+0.19%) to 89.46% when pulling 0c0c66b on dpkp:keyed_producer_failover into f206a4b on mumrah:master.

@dpkp dpkp changed the title Write a test for issue 313 - keyed producer failover Handle keyed producer failover Feb 9, 2015
@dpkp
Copy link
Owner Author

dpkp commented Feb 9, 2015

Tests pass -- ready for merge from my view

@coveralls
Copy link

Coverage Status

Coverage increased (+0.19%) to 89.46% when pulling 6ed6ad5 on dpkp:keyed_producer_failover into 3ab9a42 on mumrah:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.19%) to 89.46% when pulling 6ed6ad5 on dpkp:keyed_producer_failover into 3ab9a42 on mumrah:master.

@dpkp dpkp added the producer label Feb 9, 2015
@sontek sontek mentioned this pull request Feb 9, 2015
Merged
dpkp added a commit that referenced this pull request Feb 20, 2015
@dpkp
Merge pull request #314 from dpkp/keyed_producer_failover
9ad0be6 
Handle keyed producer failover
@dpkp dpkp merged commit 9ad0be6 into dpkp:master Feb 20, 2015
@dpkp dpkp deleted the keyed_producer_failover branch June 10, 2015 00:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
producer
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@dpkp @coveralls