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

logisland fails to start when an offset (in kafka topic) is 'invalid' #322

Open
jerome73 opened this issue Aug 29, 2017 · 0 comments
Open
Projects
Milestone

Comments

@jerome73
Copy link
Contributor

Expected behavior and actual behavior.

Logisland should be able to start whenever an offset stored in zookeeper is invalid (i-e for instance is not it the range of offsets currently available in the kafka topic.
In such case logisland should either use the earliest or latest offset from the kafka topic and start from that.

The actual behaviour shows that when dealing with an invalid offset, logisland raises a java exception and does not start.

Steps to reproduce the problem.

1- Stop logisland
2- Generate events such that the offset stored in zookeeper by logisland becomes out of the range of the offset retained by kafka
3- Restart logisland

Specifications like the version of the project, operating system, or hardware.

logisland 0.10.1
OS: all
HW: all

@oalam oalam added this to the 0.12.0 milestone Jan 25, 2018
@oalam oalam added this to To Do in Core Jan 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Core
  
To Do
Development

No branches or pull requests

2 participants