I reinstalled Kafka and it works, I work with virtual machines and someone
changed the host of one of the Kafkas without telling anybody.
2016-05-06 16:11 GMT+02:00 Cody Koeninger :
> Yeah, so that means the driver talked to kafka and kafka told it the
> highest available offset was 2723431. T
Yeah, so that means the driver talked to kafka and kafka told it the
highest available offset was 2723431. Then when the executor tried to
consume messages, it stopped getting messages before reaching that
offset. That almost certainly means something's wrong with Kafka,
have you looked at your k
This is the complete error.
2016-05-06 11:18:05,424 [task-result-getter-0] INFO
org.apache.spark.scheduler.TaskSetManager - Finished task 5.0 in stage
13.0 (TID 60) in 11692 ms on xx (6/8)
2016-05-06 11:18:08,978 [task-result-getter-1] WARN
org.apache.spark.scheduler.TaskSetManager - Lost
I think that it's a kafka error, but I'm starting thinking if it could
be something about elasticsearch since I have seen more people with
same error using elasticsearch. I have no idea.
2016-05-06 11:05 GMT+02:00 Guillermo Ortiz :
> I'm trying to read data from Spark and index to ES with its libr
I'm trying to read data from Spark and index to ES with its library
(es-hadoop 2.2.1 version).
IIt was working right for a while but now it has started to happen this error.
I have delete the checkpoint and even the kafka topic and restart all
the machines with kafka and zookeeper but it didn't fix
