You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: