Just for posterity: what happened here was an issue with the hostname
ERROR 2016-01-08 22:02:09,675 [main] [none] c.k.messaging.kafka.ConsumerGroup:
ip-10-100-102-52: ip-10-100-102-52: unknown error
! java.net.UnknownHostException: ip-10-100-102-52: unknown error
! at java.net.Inet4AddressImpl.lo
Hi Marko, this seems to have solved this. Dealing with another issue now, which
I’ll report separately.
Thank you for your help!
Cheers
Cos
On Friday, 8 January 2016 at 09:27, Cosmin Marginean wrote:
> Hi Marko, I will migrate the code and also change the timeout. thanks for
> your suggestio
Hi Marko, I will migrate the code and also change the timeout. thanks for your
suggestions. Will post a status once I’ve tested.
Cheers
Cos
On Thursday, 7 January 2016 at 22:59, Marko Bonaći wrote:
> Actually, why don't you use the same code as outlined here (that includes
> timeout in props)
Actually, why don't you use the same code as outlined here (that includes
timeout in props):
http://kafka.apache.org/090/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html
Marko Bonaći
Monitoring | Alerting | Anomaly Detection | Centralized Log Management
Solr & Elasticsearch Support
Sem
Hi Cosmin,
do you have default server configuration on these new nodes you're setting
up?
I'd check consumer's socket.timeout.ms, maybe someone set it to 30 instead
of 30 000 :)
Speaking from my own experience (I had the same symptom and this turned out
to be the cause).
Marko Bonaći
Monitoring |
Hi
I have a straightforward piece of code that creates a consumer (Kafka 0.9.0.0).
Properties props = new Properties();
props.put("zookeeper.connect", zookeeperServers);
props.put(org.apache.kafka.clients.consumer.ConsumerConfig.GROUP_ID_CONFIG,
groupId);
log.info("Starting consumer group for
