Kafka.consumer.RangeAssignor:消费者线程logstash_logstash-indexer消耗的代理分区

时间:2015-10-26 18:46:09

标签: logstash apache-kafka

我有一个ELK设置,其中一个logstash正在向Kafka推送数据,另一个logstash从Kafka提取数据。

以下是我从Kafka提取数据的logstash的Kafka输入配置: -

input {
    kafka {
        zk_connect => "kafka:2181"
        group_id => "logstash"
        topic_id => "logstash_logs"
        reset_beginning => false
        consumer_threads => 3
    }
}

我已经通过了这个github issue& &安培;我的logstash主题有3个分区。

启动logstash后,我看到以下警告,并且logstash没有从Kafka中提取任何数据: -

'[DEPRECATED] use `require 'concurrent'` instead of `require 'concurrent_ruby'`
log4j, [2015-10-27T00:11:50.471]  WARN: kafka.consumer.RangeAssignor: No broker partitions consumed by consumer thread logstash_logstash-indexer-1445884909915-d6a99924-2 for topic logstash_logs
log4j, [2015-10-27T00:11:50.471]  WARN: kafka.consumer.RangeAssignor: No broker partitions consumed by consumer thread logstash_logstash-indexer-1445884909915-d6a99924-0 for topic logstash_logs
log4j, [2015-10-27T00:11:50.471]  WARN: kafka.consumer.RangeAssignor: No broker partitions consumed by consumer thread logstash_logstash-indexer-1445884909915-d6a99924-1 for topic logstash_logs
Logstash startup completed

环境 -

  • Logstash - 1.5.3
  • Kafka - 0.8.2.1

有人能让我知道还有什么可能出错?

1 个答案:

答案 0 :(得分:0)

这已在elasticsearch discussion group中得到解答。