You mentioned that the job stopped after the "n/a" topic error, but the job
failed to recover.
What exception did you encounter in the restart executions? Was it the same
This would verify if we actually should be removing more than one of these
special MARKER partition states.
On the other hand, if I recall correctly, the Kafka consumer had a severe
bug in 1.3.0 which could lead to potential duplicate data, which was fixed
in 1.3.2. Though I don't think it is related to the error you encountered, I
strongly recommend that you use 1.3.2 instead.
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/